Carrying case with peek functionality

ABSTRACT

A carrying case with peek functionality is provided. The carrying case comprises: a device holding portion configured to receive a mobile device, the device holding portion comprising a gap for exposing an indicator of the mobile device; and a sliding portion configured to move between a closed position and an open position, the sliding portion obscuring the gap in the closed position and exposing at least a portion of the gap in the open position, the sliding portion being about planar.

FIELD

The specification relates generally to mobile devices, and specificallyto a device for providing notifications while mated with a carryingcase.

BACKGROUND

The evolution of computers is currently quite active in the mobiledevice environment. Notification indicators, such as displays, lights,light emitting diodes (LEDs) and the like can be obscured by thelocation of the mobile device mated with a carrying case.

BRIEF DESCRIPTIONS OF THE DRAWINGS

For a better understanding of the various implementations describedherein and to show more clearly how they may be carried into effect,reference will now be made, by way of example only, to the accompanyingdrawings in which:

FIG. 1 depicts a block diagram of a device for providing notificationswhen mated with a carrying case, according to non-limitingimplementations.

FIG. 2 depicts a sequence showing the device of FIG. 1 being mated witha carrying case and providing notifications when the carrying case is inan open configuration, according to non-limiting implementations.

FIG. 3 depicts a flow chart of a method for providing notifications atthe device of FIG. 1 when mated with a carrying case, according tonon-limiting implementations.

FIG. 4 depicts a block diagram of an alternative device for providingnotifications when mated with a carrying case, according to non-limitingimplementations.

FIG. 5 depicts a sequence showing the device of FIG. 4 being mated wicarrying case and providing notifications when the carrying case is inan open configuration, according to non-limiting implementations.

FIG. 6 depicts information provided at a display of the device of FIG. 4when the device is mated with the carrying case of FIG. 5, and thecarrying case is in an open configuration, according to non-limitingimplementations.

FIG. 7 depicts a block diagram of an alternative device for providingnotifications when mated with a carrying case, according to non-limitingimplementations.

FIG. 8 a depicts the device of FIG. 7 mated with a first carrying casein a first orientation

FIG. 8 b depicts the device of FIG. 7 mated with a second carrying casein a second orientation, according to non-limiting implementations.

FIG. 9 depicts a block diagram of an alternative device for providingnotifications when mated with a carrying case, according to non-limitingimplementations.

FIG. 10 a depicts the device of FIG. 9 mated with a first carrying casein a first orientation, according to non-limiting implementations.

FIG. 10 b depicts the device of FIG. 9 mated with a second carrying casein a second orientation, according to non-limiting implementations.

FIG. 11 depicts the device of FIG. 9 mated with an alternative carryingcase in a closed configuration and an open configuration, according tonon-limiting implementations.

FIG. 12 depicts a carrying case comprising a sliding portion in a closedposition and an open position, according to non-limitingimplementations.

FIG. 13 depicts an exploded schematic view of the carrying case of FIG.13 to show a biasing mechanism, according to non-limitingimplementations.

FIG. 14 depicts, the carrying case of FIG. 12 with the sliding portionin the closed position and the open position with a mobile devicereceived therein, the mobile device receiving a call, according tonon-limiting implementations.

FIG. 15 depicts an alternative carrying case comprising sliding portionin a closed position and an open position with a mobile device receivedtherein, the mobile device receiving a call, and the carrying casecomprising an aperture correspond to a microphone of the mobile device,according to non-limiting implementations.

FIG. 16 depicts an alternative carrying case comprising a slidingportion in a closed position and an open position, according tonon-limiting implementations.

FIG. 17 depicts an alternative carrying case comprising a slidingportion in a closed position and an open position, according tonon-limiting implementations.

FIG. 18 depicts an alternative carrying case comprising a slidingportion in a closed position and an open position, according tonon-limiting implementations.

FIG. 19 depicts an alternative carrying case comprising a slidingportion in a closed position and an open position, according tonon-limiting implementations.

FIG. 20 depicts an alternative carrying case comprising a slidingportion in a closed position and an open position, with a mobile devicereceived therein, according to non-limiting implementations.

FIG. 21 depicts a device holding portion of the carrying case of FIG. 20according to non-limiting implementations.

FIG. 22 depicts a perspective side view of the carrying case of FIG. 20,according to non-limiting implementations.

FIG. 23 depicts a block diagram of a device configured to detect whenmated with a carrying case by detection of a sound pattern, according tonon-limiting implementations.

FIG. 24 depicts a system including the device of FIG. 23 and a carryingcase comprising actuator bumps for producing a sound pattern detectableat the device, according to non-limiting implementations.

FIG. 25 depicts a perspective view of an interior wall of the carryingcase of FIG. 24, and a cross-sectional view of the interior wall alongline A-A, according to non-limiting implementations.

FIG. 26 depicts the device of FIG. 24 detecting a sound pattern andcomparing the sound pattern with a stored sound pattern, according tonon-limiting implementations.

FIG. 27 depicts a system including a device and a carrying casecomprising actuator bumps for producing a sound pattern when interactingat an actuator of the device, according to non-limiting implementations.

FIG. 28 depicts a system including a device and a carrying case, thedevice comprising actuator bumps for producing a sound pattern wheninteracting at an actuator of the carrying case, according tonon-limiting implementations.

DETAILED DESCRIPTION

The present disclosure describes examples of apparatus and techniques bywhich a mobile device can automatically determine whether it is in acarrying case or not, and whether one or more indicators are exposed orobscured. The mobile device can control the functions of the indicatorsas a function of that determination.

In general, this disclosure is directed to electronic devices andcarrying cases for use with the electronic device, and particularlymobile electronic devices. In general, mobile electronic devicesrepresent electronic devices that are readily movable from place toplace. Such devices typically include an indicator for providingnotification of events at the mobile electronic device including, butnot limited to, receiving messages (e.g. emails, text messages etc.) andphone calls, calendar events, and the like. The indicator can include,for example, a display, a light and/or an LED (light emitting diode), aspeaker, a vibratory motor, and the like. When the mobile electronicdevice is placed in a quiet mode, indicators that provide notificationsthat can be heard, such as speakers etc. (and in some instances thevibratory motor) are suppressed and quiet notifications are provided viathe light/LED (typically located on a front of the mobile electronicdevice, adjacent the display) and/or the display. However, when themobile electronic device is in the quiet mode and/or placed in aholster, the quiet notifications are obscured and/or hidden, whichcauses the notifications to be missed and hence the events that causedthe notifications can also be missed. This can be especially problematicwhen the events are time specific, such as phone calls, calendarreminders and the like. This specification describes variousimplementations of a carrying case that can be mated with a mobiledevice to peek at an indicator of the mobile device for example adisplay, a light, and LED and the like.

In this specification, elements may be described as “enabled to” performone or more functions or “enabled for” such functions. In general, anelement that is enabled to perform or enabled for performing a functionis configured to perform the function, or is suitable for performing thefunction, or is adapted to perform the function, or is operable toperform the function, or is otherwise capable of performing thefunction.

Furthermore, as will become apparent, in this specification certainelements may be described as mated, coupled or connected physically,electronically, optically, communicatively, mechanically or anycombination thereof, according to context. Hence, in this disclosure,“enabled to mate” refers to a communicative coupling and typically aphysical coupling as well. In general, components that arecommunicatively coupled are configured to communicate (that is, they arecapable of communicating) in any fashion for any duration, such as byway of electric signals, optical signals, wireless signals, or anycombination thereof. The communication may be one-way or two-waycommunication. Components are “physically coupled” when they areattached or connected or joined to one another, in any fashion, whetherreleasably or substantially permanently, so that physical activity ofone component generally affects the other. The physical attachment maybe direct or by way of one or more intermediate elements. According tocontext, two components that are physically coupled may behave as asingle element. In some cases, physically coupled elements may beintegrally formed, e.g., part of a single-piece article that may sharestructures and materials. In other cases, physically coupled elementsmay comprise discrete components that may be fastened together in anyfashion. Physical coupling may also include a combination of discretecomponents fastened together, and components fashioned as a singlepiece.

In this specification, elements may be described as “obscured” and/or“exposed”. In general, an element that is obscured is one or more of notvisible to a user, not viewable, covered, blocked, concealed, hidden,and the like. Similarly, an element that is exposed is one or more ofvisible to a user, uncovered, revealed, viewable, and the like. Whetheran element is obscured or exposed may depend upon a “configuration,”that is, an arrangement of physical components, such as the arrangementof elements of a carrying case.

Also, in this specification, devices or components may be described asbeing in one or more “modes.” In general, a mode is directed to a way ormanner of operating. In one mode, functionality of one or morecomponents may be enabled to, operate in a normal fashion, for example,while in another mode, the components or portions thereof may be idle ordeactivated or enhanced. Modes involve a variety of disparate functionalelements or related functional elements. In addition, several modes mayapply to a particular function; as will be discussed below, anotification mode can refer to any of several distinct modes related tonotification, such as a customized notification mode, a peeknotification mode, a temporary notification mode, a special notificationmode notification mode, and so on.

The present specification provides a carrying case comprising: a deviceholding portion configured to receive a mobile device, the deviceholding portion comprising a gap for exposing an indicator of the mobiledevice; and a sliding portion configured to move between a closedposition and an open position, the sliding portion obscuring the gap inthe closed position and exposing at least a portion of the gap in theopen position, the sliding portion being about planar.

The device holding portion can comprise at least on wall and the gap canbe located in the front wall.

The gap can comprise one or more of an aperture in a front wall of thedevice holding portion, a cut-out of the front wall, and an opening ofthe front wall.

The device holding portion can comprises a longitudinal axis and thedevice holding portion can be configured to receive the mobile devicealong the longitudinal axis. The sliding portion can be configured tomove between the closed position and the open position along thelongitudinal axis.

The carrying case can further comprise a biasing mechanism configured tobias the sliding portion to at least the closed position.

The sliding portion can be biased towards the closed position.

The sliding portion can be biased towards both the closed position andthe open position such that when the sliding portion is displaced fromeither of the closed position and the open position, the sliding portionmoves to one of the closed position and the open position depending on aposition of the sliding portion relative to the device holding portion.

The carrying case can further comprise a biasing mechanism configured tobias the sliding portion to both the closed position and the openposition such that the sliding portion moves to one of the closedposition and the open position depending on a position of the slidingportion relative to the device holding portion.

The carrying case can further comprise a biasing mechanism configuredto: move the sliding portion to the closed position when the slidingportion is moved more than halfway from the open position towards theclosed position; and, move the sliding portion to the open position whenthe sliding portion is moved more than halfway from the closed positiontowards the open position.

The carrying case can further comprise a biasing mechanism configured tobias the sliding portion to at least the closed position.

The sliding portion can be configured to be frictionally retained atpositions between the closed position and the open position.

A size of the sliding portion can be about a same size as the gap.

The sliding portion can covers a front wall of the device holdingportion in both the open position and the closed position, the frontwall comprising the gap.

The sliding portion can comprises side walls that slide alongcorresponding side walls of the device holding portion.

The sliding portion can be configured to be operated with one hand.

The carrying case can further comprise one or more apertures in at leastone of the device holding portion and the sliding portion, the one moreapertures corresponding to one or more of a position of a speaker and amicrophone of the mobile device, when the mobile device is received bythe device holding portion.

FIG. 1 depicts a device 101 for providing notifications while mated witha carrying case and/or in a carrying case, according to non-limitingimplementations. Device 101 comprises a housing 109, which houses aprocessor 120 interconnected with a memory 122; a communicationsinterface 124; a display 126; an input device 128; a speaker 132; amicrophone 134; and an indicator 135. Although shown in FIG. 1 asdistinct elements, the display 126 may be considered as one kind ofindicator, in that a display can function to provide notification to auser. Device 101 further comprises a first detector 137 configured todetect when device 101 is mated with a carrying case, the carrying casehaving an open configuration and a closed configuration, whereinindicator 135 is hidden in the closed configuration and at leastpartially exposed in the open configuration; and, a second detector 139configured to detect when the carrying case is in the openconfiguration. Processor 120 is configured to place indicator 135 in agiven notification mode when first detector 137 detects that device 101is mated with the carrying case and second detector 139 detects that thecarrying case is in the open configuration. Communications interface 124will be interchangeably referred to as interface 124.

Processor 120 is further configured to place indicator 135 in one ormore of a sleep mode and a carrying case mode when first detector 137detects that the device is in the carrying case and second detector 139detects that the carrying case is in the closed configuration.

In some implementations, the sleep mode and the carrying case mode canbe similar and indicator 135 behaves similarly in each of these modes;in other implementations, indicator 135 can behave differently in eachof these modes. For example, in the sleep mode, indicator 135 is notused and/or not turned on, while in the carrying case mode, indicator135 is turned on only when predetermined conditions are met, which caninclude, but is not limited to, receiving a message marked “important”,receiving a phone call, and the like.

It is further appreciated that device 101 and/or indicator 135 and/ordisplay 126 can enter a notification mode: for example, in somenotification modes, processor 120 controls indicator 135 and/or display126 to provide a notification of an event, including, but not limitedto, receipt of a message (e.g. emails, text messages etc.), receipt of aphone call, a calendar event and/or a calendar event reminder asindicated in, for example, a calendar database, and the like.

However, device 101 and/or indicator 135 and/or display 126 can enter agiven notification mode different from a normal notification mode whenfirst detector 137 detects that device 101 is mated with a carrying caseand second detector 139 detects that the carrying case is in the openconfiguration, as explained in further detail below. The givennotification mode can include, but is not limited to a customizednotification mode, a peek notification mode, a temporary notificationmode, a special notification mode, and the like.

In a non-limiting example, indicator 135 can comprise a light,including, but not limited to, an LED (light emitting diode), or thelike, and processor 120 controlling indicator 135 comprises processor120 controlling the light to at least turn on to provide a notification,including, but not limited to, one or more of blink, change colour orthe like. When indicator 135 is a display 126, turning on indicator 135may include mimicking an LED, blinking, flashing, changing colour,displaying text or displaying graphics, or any combination thereof. Aswill be discussed below, turning on display 126 does not necessarilyentail turning on the entire display 126.

It is appreciated that FIG. 1 further depicts a block diagram of device101, which will be hereafter be described in further detail. It shouldbe emphasized that the structure of device 101 in FIG. 1 is purely anexample. For example, as depicted in FIG. 1, it is contemplated thatdevice 101 comprises a device that can be used for implementing bothwireless voice (e.g. telephony) and wireless data communications (e.g.email, web browsing, text, and the like), as well as any otherspecialized functions, including, but not limited, to one or more of,computing, and/or entertainment related functions.

Further, device 101 can be any type of electronic device that can beused in a self-contained manner to process applications, including butnot limited to, gaming applications. Device 101 includes, but is notlimited to, any suitable combination of mobile electronic devices,mobile communications devices, mobile computing devices, portableelectronic devices, portable computing devices, portable navigationdevices, tablet computing devices, telephones, PDAs (personal digitalassistants), cellphones, smartphones, e-readers, internet-enabledappliances and the like. It is further appreciated that some mobiledevices may be handheld, that is, sized and shaped to be held andcarried in as human hand, and used while held or carried. Other suitabledevices are within the scope of present implementations.

Device 101 comprises at least one input device 128 generally enabled toreceive input data, and can comprise any suitable combination of inputdevices, including but not limited to a keyboard, a keypad, a pointingdevice, a mouse, a track wheel, a trackball, a touchpad, a touch screenand the like. Other input devices are within the scope of presentimplementations.

Input data from input device 128 is received at processor 120 (which canbe implemented as a plurality of processors, including but not limitedto one or more central processors (CPUs). Processor 120 is configured tocommunicate with a memory 122 comprising a non-volatile storage unit(e.g. Erasable Electronic Programmable Read Only Memory (“EEPROM”),Flash Memory, and the like) and a volatile storage unit (e.g. randomaccess memory (“RAM”), and the like). Programming instructions thatimplement the functional teachings of device 101 as described herein aretypically maintained, persistently, in memory 122 and used by processor120 which makes appropriate utilization of volatile storage during theexecution of such programming instructions. In some implementations,processor 120 comprises at least a portion of memory 122, for example ason-board random access memory (RAM). It is further appreciated thatmemory 122 is an example of computer readable media that can storeprogramming instructions executable on processor 120. Furthermore,memory 122 is also an example of a memory unit and/or memory module.

In particular, it is appreciated that memory 122 stores application 145,that, when processed by processor 120, enables processor 120 to placeindicator 135 in a given notification mode when first detector 137detects that device 101 is mated with a carrying case and seconddetector 139 detects that the carrying case is in the openconfiguration. It is yet further appreciated that application 145 is anexample of programming instructions stored at memory 122.

Processor 120 can be further configured to communicate with display 126,microphone 134 and speaker 132. Display 126 comprises any suitable oneof, or combination of, CRT (cathode ray tube) and/or flat panel displays(e.g. LCDs (liquid crystal displays), plasma displays, OLED (organiclight emitting diode) displays, electrophoretic displays, capacitive orresistive touch screens, and the like). Microphone 134 comprises amicrophone for receiving sound data at device 101. Speaker 132 comprisesa speaker for providing sound data, audible alerts, audiblecommunications from remote communication devices, and the like, atdevice 101. Processor 120 can also control one or more of display 126and speaker 132 to provide notifications. Indeed, in someimplementations, display 126 and indicator 135 can be combined, asdescribed below with reference to FIGS. 4 and 5. In theseimplementations, processor 120 places at least a portion of display 126is placed in a given notification mode when first detector 137 detectsthat device 101 is mated with a carrying case and second detector 139detects that the carrying case is in the open configuration.

Interface 124 (and/or another communications interface, not depicted)can be implemented as one or more radios and/or connectors and/ornetwork adaptors, configured to wirelessly communicate with one or morecommunication networks (not depicted) and/or wireless communicationnetworks and/or wired communication networks and/or wirelesstransceivers. It will be appreciated that, in these implementations,interface 124 can be configured to correspond with network architecturethat is used to implement one or more communication links to the one ormore communication networks, including but not limited to any suitablecombination of USB (universal serial bus) cables, serial cables,wireless links, cell-phone links, cellular network links (including butnot limited to 2G, 2.5G, 3G, 4G+, UMTS (Universal MobileTelecommunications System), CDMA (Code division multiple access), WCDMA(Wideband CDMA), FDD (frequency division duplexing), TDD (time divisionduplexing), TDD-LTE (TDD-Long Term Evolution), TD-SCDMA (Time DivisionSynchronous Code Division Multiple Access) and the like, wireless data,Bluetooth links, NFC (near field communication) links, WiFi links, WiMaxlinks, packet based links, the Internet, analog networks, the PSTN(public switched telephone network), access points, and the like, and/ora combination. When interface 124 is configured to communicate with oneor more communication networks, interface 124 can comprise furtherprotocol specific antennas there for (not depicted).

Housing 109 can comprise any housing, casing, and the like, enabled tobe at least one of held and carried by a human hand. In general, housing109 houses the components of device 101; however some components can bevisible via apertures, windows and the like in housing 109. For example,display 126 is generally visible. In implementations where indicator 135comprises a light, indicator 135 is also visible.

However, indicator 135 can comprise any suitable indictor, including butnot limited to display 126, speaker 132, a light, an LED, and/or avibratory device, such as a vibration motor.

Detector 137 is generally configured to detect when device 101 is matedwith a carrying case, the carrying case having an open configuration anda closed configuration, wherein indicator 135 is hidden in the closedconfiguration and at least partially exposed in the open configuration.Detector 137 can hence comprise one or more of a proximity detector, aHall detector (presuming that carrying case into which device 101 is tobe inserted comprises a magnet), a camera device, an ambient lightsensor and the like.

Detector 139 is generally configured to detect when a carrying case withwhich device 101 has been mated is in the open configuration. Detector139 can hence comprise one or more of a proximity detector, a Halldetector (presuming that carrying case into which device 101 is to beinserted comprises a magnet), a camera device, an ambient light sensor,a thermal detector and the like.

It is yet further appreciated that both detectors 137, 139 are locatedso as to respectively detect when device 101 is mated with a carryingcase and when the carrying case is in an open configuration and/or aclosed configuration. For example, when detector 137 comprises a Halldetector, detector 137 is located at device 101 such that acomplimentary magnet at a carrying case into which device 101 is to beinserted can be detected.

Similarly, when detector 139 comprises an ambient light sensor, and acarrying case into which device 101 is to be inserted comprises a flapthat is open in the open configuration and closed in the closedconfiguration, detector 139 is located such that detector 139 is notobscured by the flap in the open configuration and obscured by the flapin the closed configuration.

While not depicted, it is yet further appreciated that device 101comprises a battery and/or a power pack, or any other suitable powersource.

In any event, it should be understood that a wide variety ofconfigurations for device 101 are contemplated.

Attention is next directed to FIG. 2, which depicts a sequence of views2-I, 2-II, 2-III in which device 101 is received in a carrying case 201,carrying case 201 comprising a holster for device 101, according tonon-limiting implementations. In view 2-I, device 101 is being matedwith/being placed into carrying case 201 as indicated by arrow 202. Inthese implementations, indicator 135 comprises one or more of a lightand an LED, detector 137 comprises a Hall detector and detector 139comprises an ambient light sensor. Detector 137 is generally internal todevice 101, and hence is depicted in stippled lines. In contrast,indicator 135 is visible via a window in housing 109, and detector 137can detect ambient light via a similar window in housing 109.

Carrying case 201 comprises a flap 203 which can be open, as in views2-I, 2-III, or closed, as in view 2-II, a front wall 205, an oppositelydisposed back wall 207 and side walls 208 connecting front wall 205 andback wall 207, such that carrying case 201 can receive device 101therein. It is further appreciated that, while not visible, carryingcase 201 comprises a bottom wall. While each of front wall 205, backwall 207 and side walls 208 (as well as the bottom wall) are depicted asbeing joined to each other along an entirety of each joining edge, inother implementations, front wall 205, back wall 207 and side walls 208(as well as the bottom wall) can be joined at only one or more portionsof the joining edges. Further each of each of front wall 205, back wall207 and side walls 208 (as well as the bottom wall) can comprise gaps,apertures and the like.

Carrying case 201 can comprise any suitable apparatus for carryingmobile device 101, including, but not limited to, a holster, a sleeve, asheath, a wallet, a folder, a portfolio, bag and/or other receptacle.Further, carrying case 201 can comprise one or more of a soft case, ahard case, a combined hard and soft case, a binder, a folio, a foliocase, a folio hardshell, a shell, a hardshell, a softshell, a cover, asoft case, a hard case and a stand.

Carrying case 201 Further comprises a magnet 209, or the like, which isgenerally internal to carrying case 201, and hence is depicted instippled lines in view 2-I, for detection by detector 137. When detector137 does not comprise a Hall detector, carrying case 201 can comprise anelement for detection by detector 137 such that detector 137 can detectwhen device 101 is mated with carrying case 201.

In view 2-II, device 101 has been received in carrying case 201 and flap203 has been closed over device 101 (which is not hence not visible inview 2-II). In other words, in view 2-II, carrying case 201 is in aclosed configuration with flap 203 closed and device 101, includingindicator 135, is obscured by flap 203.

In view 2-III, flap 203 has been opened to expose a portion of device101, including indicator 135. In other words, in view 2-III, carryingcase 201 is in an open configuration with flap open.

View 2-I further depicts locations of indicator 135, detector 139 anddetector 137 at device 101 in specific non-limiting exampleimplementation. Indicator 135 is located such that indicator 135 isexposed in carrying case 201 when carrying case 201 is in the openconfiguration, as in view 2-III, and such that indicator 135 is obscuredby carrying case 201 when carrying case 201 is in the openconfiguration, as in view 2-II. Specifically, in view 2-II, flap 203obscures indicator 135 such that indicator 135 is not visible.

However, while indicator 135 is depicted as being located at a corner ofdevice 101, indicator 135 could be located at any location on device 101that is not obscured when device 101 is received in carrying case 201and carrying case 201 is in an open configuration, including, but notlimited to, along an edge and/or side of device 101.

Detector 137 is located such that detector 137 can detect magnet 209 ofcarrying case 201 when device 101 is received therein. Hence, detector137 can detect when device 101 is mated with carrying case 201 whendetector 137 detects magnet 209. For example, in views 2-I, 2-II, it isapparent that detector 137 and magnet 209 are generally aligned whendevice 101 is received in carrying case 201 so that that detector 137can detect magnet 209. However, while detector 137 is depicted as beinglocated at about a center of device 101, detector 137 could be locatedat any location on device 101 for detecting magnet 209 and/or any otherelement for indicating that device 101 is mated with carrying case 201including, but not limited to, off-centre and/or along an edge and/orside of device 101. By locating detector 137 at about center of device101, however, detector 137 can detect magnet 209 regardless of anorientation of device 101 in carrying case 201, as magnet 209, asdepicted is located about center of carrying case 201. Another magnetcan be located at a similar position at a rear of carrying case 201 suchthat detector 137 can detect the other magnet, when received facing therear of carrying case 201; in these implementations, device 101 candetect when device 101 is mated with carrying case 201 regardless ofwhether device 101 is oriented frontwards or backwards in carrying case201.

Detector 139 is located such that detector 139 can detect whether flap203 is open or closed. In depicted implementations, detector 139 islocated adjacent indicator 135; hence, when flap 203 is closed andobscures indicator 135, detector 139 is also obscured. Hence, detector139 will detect a decrease in ambient light and/or ambient light beingbelow a respective threshold level, hence leading to a detection of flap203 being closed and/or carrying case 201 being in a closedconfiguration. Processor 120 hence places indicator 135 in one or moreof a sleep mode and a carrying case mode when detector 137 detects thatdevice 101 is mated with carrying case 201 and detector 139 detects thatcarrying case 201 is in the closed configuration. In other words, ifindicator 135 is on when flap 203 is closed, processor 120 turnsindicator 135 off in the sleep mode and/or carrying case mode, therebysaving power at device 101.

Similarly, when flap 203 is open, detector 139 will detect an increasein ambient light and/or ambient light being above a respective thresholdlevel, hence leading to a detection of flap 203 being open and/orcarrying case 201 being in an open configuration. In response, processor120 will control indicator 135 to enter a given notification mode, suchthat, when notifications are pending, indicator 135 will provide anotification 211 of such including, but not limited to turning on,flashing, changing colour and the like. Specifically, processor 120places indicator 135 in a given notification mode when detector 137detects that device 101 is mated with carrying case 201 and detector 139detects that carrying case 201 is in the open configuration.

Respective threshold levels for determining whether flap 203 is openedor closed can be the same or different. However, when the respectivethreshold levels are different, with a respective threshold level fordetermining whether flap 203 is closed is less than a respectivethreshold level for determining whether flap 203 is open.

Further, while detector 139 is depicted as being located adjacentindicator 135, detector 139 could be located at any location on device101 for determining when carrying case 201 is in an open configuration,including, but not limited to, along an edge and/or side of device 101.

In depicted implementations, display 126 is turned off and/or placed ina sleep mode and/or a carrying case mode when device 101 is received incarrying case 201 (e.g. when detector 137 detects magnet 209) anddisplay 126 is not turned on (and/or remains off and/or remains in asleep mode and/or a carrying case mode) when detector 139 detects thatflap 203 is open and/or that carrying case 201 is in an openconfiguration. For example, in view 2-I, display 126 is on, and icons213 are being rendered along with a notification 215 of message and atime, for example in a status bar.

Alternatively, processor 120 can place display 126 in a givennotification mode when first detector 137 detects that device 101 ismated with a carrying case and second detector 139 detects that thecarrying case is in the open configuration. For example, one or more ofnotification 215 and a status bar can be provided in the givennotification mode.

It is appreciated that, information depicted as being rendered atdisplay 126 in FIG. 2 is an example only and indeed information renderedat display 126 can include, but is not limited to, applicationinformation, network information, and the like.

From FIG. 2 is also apparent that that present implementations includecarrying cases in which at least a part of the carrying case can befolded or bent. While carrying case 201 is depicted as comprising a flap203, other carrying cases in present implementations can comprises acover, a foldable cover, and the like. In any event, a cover and/or aflap of carrying cases of present implementations can comprise a seamand/or can be pliable and/or otherwise bend-able; a user may fold orbend the cover and/or flap to get a peek at display 126, indicator 135and/or other indicator.

Attention is now directed to FIG. 3 which depicts a flowchartillustrating a method 300 for providing notifications at a device,according to non-limiting implementations. In order to assist in theexplanation of method 300, it will be assumed that method 300 isperformed using device 101. Furthermore, the following discussion ofmethod 300 will lead to a further understanding of device 101 and itsvarious components. However, it is to be understood that device 101and/or method 300 can be varied, and need not work exactly as discussedherein in conjunction with each other, and that such variations arewithin the scope of present implementations. It is appreciated that, insome implementations, method 300 is implemented in device 101 byprocessor 120.

It is to be emphasized, however, that method 300 need not be performedin the exact sequence as shown, unless otherwise indicated; and likewisevarious blocks may be performed in parallel rather than in sequence;hence the elements of method 300 are referred to herein as “blocks”rather than “steps”. It is also to be understood that method 300 can beimplemented on variations of device 101 as well.

At block 301, processor 120 determines whether first detector 137 isdetecting that device 101 is mated with carrying case 201; whenprocessor 120 determines that first detector 137 is detecting thatdevice 101 is mated with carrying case 201 (a “Yes” decision at block301), at block 303, processor 120 determines whether second detector 139is detecting that carrying case 201 is in an open configuration; whenprocessor 120 determines that second detector 139 is detecting thatcarrying case 201 is in an open configuration (a “Yes” decision at block303), at block 305, processor places indicator 135 and/or display 126 ina given notification mode.

However, at block 303, when processor 120 determines that seconddetector 139 is detecting that carrying case 201 is in a closedconfiguration (a “No” decision at block 303), at block 307, processor120 places indicator 135 and/or display 126 in one or more of a sleepmode and a carrying case mode.

Returning to block 301, when processor 120 determines that firstdetector 137 is detecting that device 101 is not in carrying case 201 (a“No” decision at block 301), at block 309, processor 120 placesindicator 135 and/or display 126 in a non-carrying case mode, which canbe similar or different from the given notification mode of block 305.However, it is further appreciated that the non-carrying case mode cancomprise a normal notification mode where notifications are provided atindictor 135 and/or display 126.

In general, method 300 can be repeated after any of blocks 305, 307,309. Further blocks 301, 303 can be implemented in parallel. Furtherblock 303 can be implemented prior to block 301, though it isappreciated that detector 137 detecting an open configuration (e.g. anincrease in ambient light and/or detected ambient light being above arespective threshold level) of carrying case 201 while detector 139 isdetecting that device 101 is not in carrying case 201 can causeprocessor 120 to implement block 309.

In other words, both a condition of detector 137 detecting carrying case201 and a condition of detector 139 detecting an open configuration aremet in order for processor 120 to place indicator 135 and/or display 126in a given notification mode.

Attention is next directed to FIG. 4, which is substantially similar toFIG. 1, with like elements having like numbers, however with an “a”appended thereto. FIG. 4 depicts a device 101 a comprising a housing 109a, which houses a processor 120 a interconnected with a memory 122 a; acommunications interface 124 a (interchangeably referred to as interface124 a); an indicator comprising a display 126 a for providingnotifications; an input device 128 a, a speaker 132 a; a microphone 134a, an indicator 135 a, a first detector 137 a configured to detect whendevice 101 a is mated with a carrying case, the carrying case having anopen configuration and a closed configuration, wherein indicator/display126 a is hidden in the closed configuration and at least partiallyexposed in the open configuration; and, a second detector 139 aconfigured to detect when the carrying case is in the openconfiguration. Processor 120 a is configured to place indicator/display126 a (referred to hereafter as display 126 a) in a given notificationmode when first detector 137 a detects that device 101 a is mated withthe carrying case and second detector 139 a detects that the carryingcase is in the open configuration.

Memory 122 a stores an application 145 a, similar to application 145,however, application 145 a enables processor 120 a to place display 126a in a given notification mode when first detector 137 a detects thatdevice 101 a is mated with the carrying case and second detector 139 adetects that the carrying case is in the open configuration, rather thanindicator 135 a.

Specifically, in these implementations, an indicator for notificationsis combined with display 126 a, and processor 120 a is configured tocontrol at least a portion of display 126 a to turn on and/or providenotifications in the given notification mode, as described below withreference to FIG. 5.

Further, device 101 a and/or display 126 a can enter a givennotification mode different from a normal notification mode when firstdetector 137 a detects that device 101 a is mated with a carrying caseand second detector 139 a detects that the carrying case is in the openconfiguration, as explained in further detail below. The givennotification mode can include, but is not limited to a customizednotification mode, a peek notification mode, a temporary notificationmode, a special notification mode, and the like. In other words, method300 can also be implemented in device 101 a.

Hence, attention is next directed to FIG. 5, which is substantiallysimilar to FIG. 2, with like elements having like numbers, however withan “a” appended thereto. Specifically, FIG. 5 depicts a sequence ofviews 5-I, 5-II, 5-III in which device 101 a is received in a carryingcase 201 a, carrying case 201 a comprising a holster for device 101 a,according to non-limiting implementations. In a view 5-I, device 101 ais being placed into carrying case 201 a as indicated by arrow 202 a. Asin FIG. 2, in these implementations, indicator 135 a comprises one ormore of a light and an LED, detector 137 a comprises a Hall detector anddetector 139 a comprises an ambient light sensor.

Carrying case 201 a is generally similar to carrying case 201 andcomprises a flap 203 a, a front wall 205 a, an oppositely disposed backwall 207 a and side walls 208 a connecting front wall 205 a and backwall 207 a, such that carrying case 201 a can receive device 101 atherein. Further, carrying case 201 a comprises a magnet 209 a, or thelike, which is generally internal to carrying case 201 a, and which isgenerally aligned with detector 137 a when device 101 a is receivedtherein.

In view 5-II, device 101 a has been received in carrying case 201 a andflap 203 a has been closed over device 101. In other words, in view5-II, carrying case 201 a is in a closed configuration with flap 203 aclosed. However, in contrast to device 101 and carrying case 201, flap203 a does not obscure indicator 135 a. Hence, indicator 135 a canprovide a notification 511 when notifications are pending at device 101a. Indeed, it is appreciated that indicator 135 a can providenotification 511 while device 101 a is mated with carrying case 201 a,notification 511 being exposed when flap 203 a is closed, for examplevisible to a user of device 101 a and carrying case 201 a. Further,display 126 a can be turned off.

In view 5-III, flap 203 a has been opened to expose a portion of device101 a, including at least a portion of display 126 a. In other words, inview 5-III, carrying case 201 a is in an open configuration with flap203 an open. For example, flap 203 a can be opened by a user of device101 a and carrying case 201 a in response to notification 511.

However, in contrast to view 2-III, in view 5-III processor 120 a placesdisplay 126 a in a given notification mode when first detector 137 adetects that device 101 a is mated with carrying case 201 a and seconddetector 139 a detects that carrying case 201 a is in the openconfiguration. Specifically, processor 120 a controls at least a portionof display 126 a to turn on in the given notification mode.

In some implementations, processor 120 a controls display 126 a to turnon in the given notification mode. In other words, even though theentirety of display 126 a is not visible when device 101 a is mated withcarrying case 201 a, the entire area of display 126 a can be turned onin the given notification mode; hence, even though the entirety ofdisplay 126 a is not visible in view 5-III, display 126 a can berendering both icons 213 a (not visible in view 5-III), notification 215a and time and/or a status bar.

However, in other implementations, processor 120 a controls a portion ofdisplay 126 a that is at least partially exposed in the openconfiguration to turn on in the given notification mode. For example,attention is directed to FIG. 6, which depicts device 101 a in a givennotification mode according to these implementations. Only a portion 601is turned on, portion 601 comprising notification 215 a and a time,and/or a status bar. A remaining portion 603 of display 126 a is turnedoff. In other words, portion 601 is the portion of display 126 a that isat least partially exposed when device 101 a is mated with carrying case201 a and flap 203 a is open, hence, only portion 601 is turned on,while remaining portion 603 remains off, thereby saving power at device101 a and further providing a “peek” at display 126 a.

Hence, in these implementations, processor 120 a is configured tocontrol indicator 135 a to provide notifications regardless of aconfiguration of carrying case 201 a (i.e. indicator 135 a providesnotification 511 regardless of whether flap 203 a is open or closed).Processor 120 a is further configured to control portion 601 of display126 a that is at least partially exposed in the open configuration toturn on in the given notification mode.

In some alternative implementations, indicator 135 a can turn on onlywhen carrying case 201 is in an open configuration.

Attention is next directed to FIG. 7, which is substantially similar toFIG. 4, with like elements having like numbers, however with a “b”appended thereto rather than an “a”. FIG. 7 depicts a device 101 bcomprising a housing 109 b, which houses a processor 120 binterconnected with a memory 122 b; a communications interface 124 b(interchangeably referred to as interface 124 b); an indicatorcomprising a display 126 b for providing notifications; an input device128 b; a speaker 132 b, a microphone 134 b; an indicator 135 b; a firstdetector 137 b configured to detect when device 101 b is mated with acarrying case, the carrying case having an open configuration and aclosed configuration, wherein indicator/display 126 b is hidden in theclosed configuration and at least partially exposed in the openconfiguration; and, a second detector 139 b configured to detect whenthe carrying case is in the open configuration. Processor 120 b isconfigured to place indicator/display 126 b in a given notification modewhen first detector 137 b detects that device 101 b is mated with thecarrying case and second detector 139 b detects that the carrying caseis in the open configuration. Memory 122 b stores an application 145 b,similar to application 145 a.

Further, device 101 b and/or display 126 b can enter a givennotification mode different from a normal notification mode when firstdetector 137 b detects that device 101 b is mated with a carrying caseand second detector 139 b detects that the carrying case is in the openconfiguration, as explained in further detail below. The givennotification mode can include, but is not limited to a customizednotification mode, a peek notification mode, a temporary notificationmode, a special notification mode, and the like. In other words, method300 can also be implemented in device 101 b.

However, in these implementations device 101 b further comprises anorientation sensor 711 for detecting an orientation of device 101 b.Orientation sensor 711 can comprise one or more of an accelerometer, amagnetometer and the like. In particular, orientations sensor 711 candetect whether device 101 b is in a landscape orientation (e.g. a longaxis of device 101 b and/or display 126 b being generally parallel withthe ground) or a portrait orientation (e.g. a long axis of device 101 band/or display 126 b being generally perpendicular with the ground). Inthese implementations, processor 120 b is further configured to providenotifications in a portion of display 126 b that is at least partiallyexposed in the open configuration based on the orientation of device 101b.

For example, attention is next directed to FIG. 8 a, which depictsdevice 101 b in a carrying case 201 b-1 that is similar to carrying case201 a, comprising a flap 203 b-1 and a magnet 209 b-1 respectivelysimilar to flap 203 a and magnet 209 a. It is appreciated that carryingcase 201 b-1 further comprises a front wall, an opposing back wall, sidewalls and a bottom wall. It is appreciated that in FIG. 8 a, carryingcase 201 b-1 is in an open configuration as flap 203 b-1 is open,exposing at least a portion of display 126 b. As in view 5-III,processor 120 b controls at least a portion of display 126 b that is atleast partially exposed in the open configuration to turn on in thegiven notification mode to render notification 215 b, similar tonotification 215 a, and a time, and/or a status bar.

It is appreciated that orientation sensor 711, while not depicted,detects that device 101 a is a landscape orientation with a right sideof device 101 b being upwards, and hence, processor 120 b controlsdisplay 126 b to provide notification 215 b and time in a landscapeorientation along the edge of display 126 b that is upmost.

In contrast, FIG. 8 b depicts device 101 b in another carrying case 201b-2 that is similar to carrying case 201 a, comprising a flap 203 b-2and a magnet 209 b-2 respectively similar to flap 203 a and magnet 209a. It is appreciated that carrying case 201 b-2 further comprises afront wall, an opposing back wall, side walls and a bottom wall.However, carrying case 201 b-2 is configured to receive device 101 b ina portrait orientation.

It is appreciated that in FIG. 8 b, carrying case 201 b-2 is in an openconfiguration as flap 203 b-2 is open, exposing at least a portion ofdisplay 126 b; however, the portion of display 126 b exposed when device101 b is mated with carrying case 201 b-2 is different from carryingcase 201 b-2, as carrying case 201 b-2 receives device 101 b in aportrait orientation. Nonetheless, processor 120 b controls at least aportion of display 126 b that is at least partially exposed in the openconfiguration to turn on in the given notification mode to rendernotification 215 b, similar to notification 215 a, and a time, and/or astatus bar.

It is appreciated that orientation sensor 711, while not depicted,detects that device 101 b is a portrait orientation with a top side ofdevice 101 b being upwards, and hence, processor 120 b controls display126 b to provide notification 215 b and time in a portrait orientationalong the edge of display 126 b that is upmost.

An issue, however, with using an orientation sensor to determine whichportion of display 126 b to place in a given notification mode, is thatif carrying case 201 b-1 was reoriented from a landscape orientation toa portrait orientation, with device 101 b therein, processor 120 b couldcontrol display 126 b to place a portion of display 126 b into a givennotification mode that is not visible when carrying case 201 b-1 is inan open configuration. Hence, for example, the portion of display 126 bthat is in the given notification mode in FIG. 8 b could be turned onwhile device 101 b is mated with carrying case 201 b-1, and notification215 b may not be visible.

Hence, attention is next directed to FIG. 9, which is substantiallysimilar to FIG. 4, with like elements having like numbers, however witha “c” appended thereto rather than an “a”. FIG. 9 depicts a device 101 ccomprising a housing 109 c, which houses a processor 120 cinterconnected with a memory 122 c; a communications interface 124 c(interchangeably referred to as interface 124 c); an indicatorcomprising a display 126 c for providing notifications; an input device128 c; a speaker 132 c; a microphone 134 c; an indicator 135 c; a firstdetector 137 c configured to detect when device 101 c is mated with acarrying case, the carrying case having an open configuration and aclosed configuration, wherein indicator/display 126 c is hidden in theclosed configuration and at least partially exposed in the openconfiguration; and, a second detector 139 c configured to detect whenthe carrying case is in the open configuration. Processor 120 c isconfigured to place indicator/display 126 c in a given notification modewhen first detector 137 c detects that device 101 c is mated with thecarrying case and second detector 139 c detects that the carrying caseis in the open configuration. Memory 122 c stores an application 145 c,similar to application 145 a.

Further, device 101 c and/or display 126 c can enter a givennotification mode different from a normal notification mode when firstdetector 137 c detects that device 101 c is mated with a carrying caseand second detector 139 c detects that the carrying case is in the openconfiguration, as explained in further detail below. The givennotification mode can include, but is not limited to: a customizednotification mode, a peek notification mode, a temporary notificationmode, a special notification mode, and the like. In other words, method300 can also be implemented in device 101 c.

However, in these implementations device 101 c further comprises adetector 911 configured to detect a type of carrying case with whichdevice 101 c is mated. In general detector 911 is configured to detect atype of carrying case with which device 1010 is mated by detecting acorresponding element at the carrying case. For example, detector 911can comprise one or more of an optical detector, a near fieldcommunication (NFC) detector, a radio frequency identification (RFID)detector, and the like; hence, a carrying case with which device 101 cis to be mated can comprise one or more of an optical identifier and/ortag, an NFC tag, and RFID tag and the like, detectable by detector 911(e.g. respectively detectable by the optical detector, the NFC detector,and the RFID detector). Processor 120 can be configured to control atleast a portion of indicator/display 126 c that is at least partiallyexposed in the open configuration to turn on in the given notificationmode, based on the type of the carrying case.

For example, attention is next directed to FIG. 10 a, which depictsdevice 101 e in a carrying case 201 c-1 that is similar to carrying case201 a, comprising a flap 203 c-1 and a magnet 209 c-1 respectivelysimilar to flap 203 a and magnet 209 a. It is appreciated that carryingcase 201 c-1 further comprises a front wall, an opposing back wall, sidewalls and a bottom wall. It is appreciated that in FIG. 10 a, carryingcase 201 c-1 is in an open configuration as flap 203 c-1 is open,exposing at least a portion of display 126 c.

As in view 5-III, processor 120 c controls at least a portion of display126 c that is at least partially exposed in the open configuration toturn on in the given notification mode to render notification 215 c,similar to notification 215 a, and a time, and/or a status bar. It isappreciated, however, that carrying case 201 c-1 further comprises anelement 1011-1 that is detectable by detector 911, each of which arerespectively located at carrying case 201 c-1 and device 101 c such thatthey are generally aligned when device 101 c is mated with carrying case201 c-1.

In general element 1011-1 stores data and/or has data encoded thereinand/or has data encoded thereon, identifying at least a type of carryingcase 201 c-1, the data detectable by detector 911. For example, whendetector 911 comprises an NFC detector, element 1011-1 comprises an NFCtag storing data comprising one or more of a type of carrying case 201c-2 and an identifier of carrying case 201 c-1 such the data can beretrieved at device 101 c by detector 911. Similarly, when detector 911comprises an RFID detector, element 1011-1 comprises an RFID tag storingdata comprising one or more of a type of carrying case 201 c-2 and anidentifier of carrying case 201 c-1 such the data can be retrieved atdevice 101 c by detector 911. Similarly, when detector 911 comprises anoptical detector, element 1011-1 comprises an optical identifier/tagonto which can be printed data comprising one or more of a type ofcarrying case 201 c-2 and an identifier of carrying case 201 c-1 suchthe data can be retrieved at device 101 c by detector 911.

From the data received from element 1011-1, processor 120 c candetermine that carrying case 201 c-1 mates with device 101 c in alandscape orientation and further determine a portion of display 126 cthat is exposed when carrying case 201 c-1 is in an open configuration.Display 126 c can be controlled accordingly.

For example, memory 122 c can store information relating carrying casetypes to a portion of display 126 c that is to be controlled when device101 c is mated with a carrying case of given types.

Hence, when device 101 c receives data from element 1011-1, processor120 c can determine that, in the given notification mode, notificationsare to be provided in a landscape orientation at a top portion ofdisplay 126 c. Processor 120 c can further determine from data receivedfrom element 1011-2 what portion of display 126 c to control to providenotifications and optionally what portion of display 126 c that is toremain off in a given notification mode. In other words, processor 120 ccan further determine what portion of display 126 c is at leastpartially exposed when device 101 c is mated with carrying case 201 c-1.

Similarly, FIG. 10 b depicts device 101 c mated with another carryingcase 201 c-2 that is similar to carrying case 201 a, comprising a flap203 c-2 and a magnet 209 c-2 respectively similar to flap 203 a andmagnet 209 a. It is appreciated that carrying case 201 c-2 furthercomprises a front wall, an opposing back wall, side walls and a bottomwall. However, carrying case 201 c-2 is configured to mate with device101 c in a portrait orientation. Carrying case 201 c-2 comprises anelement 1011-2, similar to element 1011-1, however element 1011-2comprises data indicating a type of carrying case 201 c-2. Hence, whendevice 101 c receives data from element 1011-2 via detector 911,processor 120 c can determine that, in a given notification mode,notifications are to be provided in a portrait orientation at a topportion of display 126 c. Further, processor 120 c can further determinewhat portion of display 126 c is at least partially exposed when device101 c is mated with carrying case 201 c-2 and provide notifications inthe portion of display 126 c that is at least partially exposed.

Attention is next directed to FIG. 11 which depicts a view 11-I ofdevice 101 c mated with a carrying case 201 d in a closed configuration,and a view 11-II of device 101 c mated with carrying case 201 d in anopen configuration.

Carrying case 201 d comprises one or more of a holder, a holster andlike, with an open top for inserting and removing device 101 c, and anelement 1111 similar to elements 1011-1, 1011-2. Carrying case 201 dfurther comprises a sliding portion 1113 at a front wall 205 d ofcarrying case 201 d, sliding portion 1113 configured to slide alongfront wall 205 d to an open configuration, as depicted in view 11-II,thereby exposing at least a portion of display 126 c of device 101 c. Indepicted implementations, sliding portion 1113 slides in a direction ofarrow 1115 (e.g. down, as depicted) to expose at least a portion ofdisplay 126 c. In general sliding portion 1113 slides between the closedconfiguration of view 11-I and the open configuration of view 11-II.

In some implementations sliding portion 1113 can be biased towards theclosed configuration. While not depicted, it is further appreciated thatcarrying case 201 d comprises apparatus for enabling sliding portion1113 to slide between the closed configuration and the openconfiguration, and optionally for biasing sliding portion 1113 towardsthe closed position.

In any event, comparing FIG. 11 with FIGS. 10 a, 10 b, it is appreciatedthat, as depicted, a larger portion of display 126 c is exposed in theopen configuration of carrying case 201 d than in the open configurationof carrying cases 201 c-1, 201 c-2. Hence, processor 120 c can control alarger portion of display 126 c to provide notifications when device 101c is mated with carrying case 201 d as compared to when device 101 d ismated with carrying cases 201 c-1, 201 c-2.

For example, as depicted in view 11-II, processor 120 c controls display126 c to provide additional information associated with notifications inthe exposed portion of display 126 c, for example, “New Email From Sue”.It is appreciated that processor 120 c controls display 126 c based ondata received from element 1111. It is further appreciated that a typeof data displayed can be configured at application 145 c and based on anamount of display 126 c that is exposed in a given carrying case.

Persons skilled in the art will appreciate that there are yet morealternative implementations and modifications possible. It isappreciated that heretofore it has been assumed that each of devices101, 101 a, 101 b, 101 c, is mated with a respective carrying case in aparticular orientation relative to the respective carrying case. Forexample, returning to FIG. 2, device 101 is mated with carrying case 201with indicator 135 adjacent flap and display 126 facing front wall 205in a landscape orientation. However, when device 101 is mated withcarrying case 201 in a different orientation, for example, device 101facing back wall 207, and/or device 101 inserted into carrying case 201upside down, depending on locations and/or orientations of detectors137, 139, magnet 209 etc., processor 120 may detect that device 101 ismated with carrying case 201 and may further detect that flap 203 isopen. In these situations, indicator 135 would be controlled to providenotifications even though indicator 135 may not be visible. Similarsituations can occur with each of devices 101, 101 a, 101 b, 101 c.

To mitigate such false positives, one or more of devices 101, 101 a, 101b, 101 c can further comprise a detector for determining an orientationof a device relative to a mated carrying case and provide notificationsonly when the orientation of the device is such that at least a portionof the indicator is exposed when the mated carrying case is in an openconfiguration. Such detectors can include any suitable combination ofambient light sensors, cameras, orientation sensors, NFC detectors, RFIDdetectors, optical sensors and the like. In some of theseimplementations, a respective mated carrying case can comprise elementsfor detection to assist a device in determining a relative orientationwhen mated with the respective carrying case.

Alternatively, the orientation of a device relative to a mated carryingcase can be used by a respective processor to determine a portion of arespective display that is to be placed in a given notification mode.For example, attention is again directed to view 11-II; it is presentlyfurther assumed that processor 120 c can determine: when device 101 c ismated with carrying case 201 d; and when carrying case 201 d is in anopen configuration, regardless of an orientation of device 101 c incarrying case 201 d. It is further presumed that device 101 c furthercomprises one or more detectors for detecting a relative orientation ofdevice 101 c in carrying case 201 d.

In any event, in these implementations, when display 126 c is facing aback wall of carrying case 201 d and is not exposed regardless of aconfiguration of carrying case 201 d, processor 120 c leaves display 126c in one or more of a sleep mode and a carrying case mode, for example,turning display 126 c off. However, when display 126 c is upside down,relative to the orientation of device 101 c in view 11-II, but at leasta portion of display 126 c is exposed (i.e. display 126 c is facingfront wall 205 d), processor 120 c places the exposed portion of display126 c in a given notification mode.

Attention is next directed to FIG. 12 which depicts views 12-I, 1241 ofa carrying case 1201, similar to carrying case 201 d in, respectively, aclosed configuration and an open configuration, according tonon-limiting implementations. Carrying case 1201 comprises: a deviceholding portion 1202 configured to receive a mobile device (notdepicted, but similar to devices 101, 101 a, 101 b, 101 c), deviceholding portion 1202 comprising at least a front wall 1205 and a gap1206 in front wall 1205 for exposing an indicator of the mobile device,for example as in FIG. 11. Carrying case 1201 further comprises asliding portion 1203 configured to move between a closed position and anopen position, sliding portion 1203 obscuring gap 1206 in the closedposition and exposing at least a portion of gap 1206 in the openposition, sliding portion 1203 being about planar. Sliding portion 1203is in the closed position in view 12-I and in the open position in view12-II.

Device holding portion 1202 generally comprises front wall 1205 and gap1206 therein as well as an opposing back wall 1207, side walls 1209-1,1209-2 joining front wall 1205 to back wall 1207, and a bottom wall 1211such that carrying case 1201 can receive a mobile device therein. Sidewalls 1209-1, 1209-2 will be interchangeably referred to hereafter,collectively, as side walls 1209 and generically as a side wall 1209.While each of front wall 1205, back wall 1207, side walls 1209 andbottom wall 1211 are depicted as being joined to each other along anentirety of each joining edge, in other implementations, front wall1205, back wall 1207, side walls 1209, and bottom wall 1211 can bejoined at only one or more portions of the joining edges. Further eachof front wall 1205, back wall 1207, side walls 1209 and bottom wall 1211can comprise gaps, apertures and the like, other than gap 1206.

In depicted implementations, gap 1206 comprises a cut-out of front wall1205, however, in other implementations, gap 1206 can comprise one ormore of an aperture in front wall 1205 (for example see FIG. 17described below), a cut-out of front wall 1205, a window in front wall1205, and an opening in front wall 1205.

Regardless of whether gap 1206 comprises an aperture, a cut-out, awindow or like, it is appreciated that one or more of walls 1205, 1209form edges of gap 1206, and alternatively carrying case 1206 cancomprise arms, edges, extensions and the like from one or more of walls1205, 1209 configured to form gap 1206. Indeed, it is appreciated thatdevice holding portion 1202 can form gap 1206, and that gap 1206 cancomprise one or more of an opening, an aperture, a cut-out, a window andthe like.

Further, carrying case 1201 can comprise one or more of a soft case, ahard case, a combined hard and soft case, a binder, a folio, a foliocase, a folio hardshell, a shell, a hardshell, a softshell, a cover, asoft case, a hard case and a stand. Carrying case 1201 can further bemanufactured from any combination of plastic, plastic, polycarbonate,plastic, metal, leather, and the like.

In any event, sliding portion 1203 is generally enabled to move betweenthe closed position, as in view 12-I, and the open position, as in view12-II. For example, arrow 1215-1 in view 12-I indicates that slidingportion 1203 is moveable to the open position from the closed position,and arrow 1215-2 in view 12-II indicates that sliding portion 1203 ismoveable to the closed position from the open position.

From at least view 12-I, it is apparent that device holding portion 1202comprises a longitudinal axis 1217 (i.e. carrying case 1201 in general,and device holding portion 1202 in particular, has a length, and a widththat is less than the length).

Further, in depicted implementations, device holding portion 1202 isconfigured to receive a mobile device along longitudinal axis 1217. Inother words, device holding portion 1202 is at least partially open atan end opposite bottom wall 1211 such that a mobile device can bereceived therein.

From views 12-I, 12-II, it is yet further appreciated that, in depictedimplementations, sliding portion 1203 is configured to move between theclosed position and the open position along longitudinal axis 1217.

From FIG. 12, it is apparent that sliding portion 1203 is about planarand that sliding portion 1203 generally retains its shape as slidingportion 1203 moves between the closed position and the open position.For example, while sliding portion 1203 can be bendable, such bendingdoes not generally contribute to the movement between the closedposition and the open position.

In implementations depicted in FIG. 12, front wall 1205 and slidingportion 1203 are configured such that sliding portion 1203 slides alongan exterior side of front wall 1205 between the closed position and theopen position. In other implementations, however, front wall 1205 andsliding portion 1203 are configured such that sliding portion 1203slides along an interior side of front wall 1205 between the closedposition and the open position: in these implementations, slidingportion 1203 will slide between front wall 1205 and a mobile devicereceived at device holding portion 1202. In yet further implementations,front wall 1205 and sliding portion 1203 are configured such thatsliding portion 1203 slides into front wall 1205 in the closed position;in these implementations, front wall 1205 can comprise a receptacle forreceiving sliding portion 1203.

Regardless of the specific configuration of front wall 1205 and slidingportion 1203, it is appreciated that sliding portion 1203 is generallyconfigured to be operated with one hand. In other words, carrying case1201 me be generally configured to be handheld, that is, sized andshaped to be held and carried in as human hand, and used while held orcarried. Furthermore, sliding portion 1203 is generally configured tomove between the closed position and the open position when actuated bya finger and/or a thumb of a hand holding carrying case 1201. Forexample, a user holding carrying case 1201 can use their thumb, or thelike, to apply sliding pressure to sliding portion 1203 to move slidingportion 1203 between the closed position and the open position.

In some implementations, sliding portion 1203 can be biased towards theclosed position. In other words, when a user apples sliding pressure tosliding portion 1203 to move sliding portion 1203 to the open position,once the sliding pressure is released, sliding portion 1203 moves backto the closed position.

In yet further implementations, sliding portion 1203 can be biasedtowards both the closed position and the open position such that whensliding portion 1203 is displaced from either of the closed position andthe open position, sliding portion 1203 moves to one of the closedposition and the open position depending on a position of slidingportion 1203 relative to device holding portion 1202. For example, insome of these implementations, when sliding portion 1203 is displacedfrom the closed position more than halfway towards the open position andreleased, then sliding portion 1203 will move to the open position.Similarly, in these implementations, when sliding portion 1203 isdisplaced from the open position more than halfway towards the closedposition and released, then sliding portion 1203 will move to the closedposition. In this manner, sliding portion 1203 can be “snapped” to oneor the other of the closed position and the open position.

Hence, carrying case 1201 can further comprise a biasing mechanism 1301,as depicted in FIG. 13, which depicts an exploded schematic view ofcarrying case 1201, but is otherwise similar to view 12-I with likeelements having like numbers. As depicted, carrying case 1201 comprisesbiasing mechanism 1301 that includes a leaf spring 1303 and attachmentportions 1305-1, 1305-2 respectively located at opposite ends of leafspring 1303, attachment portions 1305-1, 1305-2 for respectivelyattaching a first end of leaf spring 1303 to front wall 1205 and anopposite end of leaf spring 1303 to sliding portion 1203. Attachmentportions 1305-1, 1305-2 can be configured to, pivot as sliding portion1203 moves between the closed position and the open position.

In any event, biasing mechanism 1301 is depicted in two positions inFIG. 13: a first position depicted in solid lines and a second positiondepicted in broken lines. The first position of biasing mechanism 1301corresponds to the closed position of sliding portion 1203 in view 12-I,while the second position of biasing mechanism 1301 corresponds to theopen position of sliding portion 1203 in view 12-II.

Biasing mechanism 1301 can be generally configured to bias slidingportion 1203 to at least the closed position, depicted in view 12-I.However, as described above, biasing mechanism 1301 can be configured tobias sliding portion 1203 to both the closed position depicted in view12-I and the open position depicted in view 12-II such that slidingportion 1203 moves to one of the closed position and the open positiondepending on a position of sliding portion 1203 relative to deviceholding portion 1202. Hence, in these implementations, biasing mechanism1301 comprises two equilibrium positions: the first position and thesecond position, and will move back and forth between to one of thefirst position and the second position depending displacement of thebiasing mechanism 1301.

While in depicted implementations, biasing mechanism 1301 comprises aleaf spring 1303 in other implementations, biasing mechanism 1301 caninclude, but is not limited to, one or more of a spring, a leaf spring,a slider device, and the like. For example, biasing mechanism 1301 cancomprise a slider similar to that used on slider mobile electronicdevices, slider keyboards and the like.

While not depicted, it is further appreciated that carrying case 1201can comprise rails, and the like, at one or more of sliding portion1203, front wall 1205 and side walls 1209, and that sliding portion 1203can move between the closed position and the open position on the rails.

It is further appreciated that sliding portion 1203 need not be biasedto one or more the closed position and the open position. Rather, in yetfurther implementations, sliding portion 1203 can comprise a frictionthat slider that can be frictionally retained at positions between theclosed position and the open position.

Attention is next directed to FIG. 14, which is substantially similar toFIG. 12, with like elements having like numbers and depicts carryingcase 1201 and device 101 c received in device holding portion 1202,carrying case 1201 being held by a hand 1401. In view 14-I of FIG. 14,sliding portion 1203 is in the closed position and in view 14-II,sliding portion 1203 is the open position. When device 101 c is receivedin device holding portion 1202, and when sliding portion 1203 in theclosed position, as in view 14-I, sliding portion 1203 obscures gap1206, and hence further obscures an indicator at device 101 c, forexample display 126 c. In view 14-I, however, device 101 c is receivinga call, as indicated by notification 1403, which can comprises an auralnotification (e.g. device 101 c is “ringing”) and/or a visualnotification (e.g. a light at device 101 c is flashing). Hence, the userholding carrying case 1201 uses a thumb of hand 1401 to move slidingportion 1203 to the open position, as indicated by arrow 1405 to viewand/or “peek” at display 126 c, rather than removing device 101 c atleast partially from carrying ease 1201 to view display 126 c.

However, notification 1403 can also be provided when any event occurs atdevice 101 c, including, but not limited to receiving a message, acalendar event, and the like.

Furthermore, in some implementations, one or more of sliding portion1203 and/or device 101 c can be configured such that indicator 135 c ofdevice 101 c is exposed when sliding portion is in the closed position.For example, indicator 135 c an be located at device 101 c such thatindicator 135 c is not obscured when sliding portion 1203 is in theclosed position, for example indicator 135 c can be located on a topside of device 101 c. Alternatively, a shape of sliding portion 1203 canbe configured such that indicator is not obscured in the open position:for example, sliding portion 1203 can comprise a cut-out, an apertureand the like corresponding to a position of indicator 135 c when device101 c is received in carrying case 1201 and sliding portion 1203 is inthe closed position. In yet a further alternative, sliding portion 1203can be at least partially transparent in at least an area correspondingto a position of indicator 135 c when device 101 c is received incarrying case 1201 and sliding portion 1203 is in the closed position.Regardless, in these implementations, indicator 135 c can be controlledto provide a visual notification of an event at device 101 c, either inaddition to notification 1403 or in place of notification 1403, forexample indicator 135 c can comprise a light which can be controlled toblink, change colour and the like to provide the visual notification.

When sliding portion 1203 is moved to the open position, as in view14-II, gap 1206 is exposed and further at least a portion ofindicator/display 126 c of device 101 c is exposed. It is appreciatedthat a location of gap 1206 generally corresponds to a location of anindicator and/or at least a portion of display 126 c when device 101 cis received in device holding portion 1202.

Hence, carrying case 1201 can be used to “peek” at indicator/display 126c of device 101 c by moving sliding portion 1203 to the open position.Specifically, as depicted, a user can move sliding portion 1203 from theclosed position to the open position in order to “peek” at display 126 cof device 101 c through gap 1206 (not numbered in FIG. 14, but assumedto be) to view caller ID (identification) information. In other words,device 101 c determines that carrying case 101 c is in an openconfiguration and controls display 126 c to a given notification mode,as described above.

In depicted implementations, the given notification mode of display 126c includes the caller ID information (e.g. “Call from Sally”) and avirtual “Answer” button 1407 which, when actuated, causes the call to beanswered at device 101 c.

However, moving sliding portion 1203 to the open position can be used togenerally “peek” at display 126 c of device 101 c, regardless of whethera phone call is received or not. For example, when carrying case 1201 isused with device 101 c, device 101 c can detect when sliding portion1203 is in the open position (e.g. carrying case 1201 is in an openconfiguration) and indicator/display 126 c of device 101 c can be placedin a given notification mode as described above. Indeed, carrying case1201, with device 101 c, received therein, can together be elements of asystem for providing a “peek” at display 126 c of device 101 c.

Attention is next directed to FIG. 15, which is substantially similar toFIG. 14, with like elements having like numbers, however FIG. 15 depictsa carrying case 1501 with device 101 c received in a device holdingportion 1502 of carrying case 1501, with view 15-I showing a slidingportion 1503 of carrying case 1501 in a closed configuration and view15-II showing sliding portion 1503 in an open configuration. In otherwords, carrying case 1501 is substantially similar to carrying case1201; however, in these implementations, carrying case 1501 comprises anaperture 1550 in a front wall 1505 of carrying case 1501 correspondingto microphone 134 c of device 101 c when device 101 c is received indevice holding portion 1502. Hence, when button 1407 is actuated toanswer the call, a user can use speaker 132 c, which is exposed whensliding portion 1503 is in the open position, and microphone 134 c torespectively listen and talk on the call. It is appreciated thataperture 1550 can comprise a screen, a grill and the like configured forsound to pass there through but generally protect microphone 134 c.

In implementations where speaker 132 c is obscured by carrying case 1501when sliding portion 1503 is in the open position, carrying case 1501can further comprise an aperture corresponding to speaker 132 c.

Indeed, it is appreciated that each carrying case described herein cancomprise one or more apertures in at least one of a device holdingportion, a sliding portion, a flap, a wall etc., the one more aperturescorresponding to one or more of a position of a speaker and a microphoneof a device, when the device is received by the carrying case, a deviceholding portion and the like.

It is yet further appreciated that each device described herein can beconfigured to access to given functionality in the described givennotification modes, for example to answer a call, an email, a message, atext message and the like. In some of the given notification modes,voice recognition techniques can be used to provide the givenfunctionality when an exposed area of a display that is placed in thegiven notification mode is too small to provide a virtual keyboard, andthe like.

In yet further implementations, each device described herein can befurther configured to automatically implement a function when the devicedetects that it is mated with a carrying case and that the carrying caseis in an open configuration. For example, with reference to FIG. 15, inan alternative implementation, device 101 c can be configured to answerthe call (i.e. implement a function) when sliding portion 1503 is movedto the open position.

Further, the function that is automatically implemented at device 101 c(and the like) can further depend on a state of device 101 c whensliding portion 1503 (and the like) is moved to the open position and/orwhen the carrying case is in an open configuration. For example, whendevice 101 c is in a state of receiving a call when sliding portion 1503is moved to the open position, device 101 c can answer the call whensliding portion 1503 is moved to the open position and/or when thecarrying case is placed in an open configuration. Alternatively, whendevice 101 c has received a message within a given time period beforesliding portion 1503 is moved to the open position, device 101 c canimplement a message answer function when sliding portion 1503 is movedto the open position and/or when the carrying case is placed in an openconfiguration. In some implementations, device 101 c can store, rulesand the like, at memory 122 c indicating which function is to beimplemented when device 101 c is in a given state when sliding portion1503 is moved to the open position, and/or when a carrying case isplaced in an open configuration.

Attention is next directed to FIG. 16 which depicts views 16-I, 16-II ofan alternative implementation of a carrying case 1601, respectively, ina closed configuration and an open configuration, according tonon-limiting implementations. Carrying case 1601 is generally similar tocarrying case 1201 with like elements having like numbers, howeverpreceded by “16” rather than “12”. Hence, carrying case 1601 comprises:a device holding portion 1602 configured to receive a mobile device (notdepicted, but similar to devices 101, 101 a, 101 b, 101 c), deviceholding portion 1602 comprising at least a front wall 1605 and a gap1606 in front wall 1605 for exposing an indicator of the mobile device,for example as in FIG. 14. Carrying case 1601 further comprises asliding portion 1603 configured to move between a closed position and anopen position, sliding portion 1603 obscuring gap 1606 in the closedposition and exposing at least a portion of gap 1606 in the openposition, sliding portion 1603 being about planar. Sliding portion 1603is in the closed position in view 16-I and in the open position in view16-II.

Device holding portion 1602 generally comprises front wall 1605 and gap1606 therein as well as an opposing back wall 1607, side walls 1609-1,1609-2 joining front wall 1605 to back wall 1607, and a bottom wall 1611such that carrying case 1601 can receive a mobile device therein. Sidewalls 1609-1, 1609-2 will be interchangeably referred to hereafter,collectively, as side walls 1609 and generically as a side wall 1609.While each of front wall 1605, back wall 1607, side walls 1609 andbottom wall 1611 are depicted as being joined to each other along anentirety of each joining edge, in other implementations, front wall1605, back wall 1607, side walls 1609, and bottom wall 1611 can bejoined at only one or more portions of the joining edges. Further eachof front wall 1605, back wall 1607, side walls 1609 and bottom wall 1611can comprise gaps, apertures and the like, other than gap 1606.

From at least view 16-I, it is apparent that device holding portion 1602comprises a lateral axis 1617 (i.e. carrying case 1601 in general, anddevice holding portion 1602 in particular, has a length, and a widththat is less than the length, lateral axis 1617 along the width).

Further, in depicted implementations, device holding portion 1602 isconfigured to receive a mobile device along lateral axis 1617. In otherwords, device holding portion 1602 is at least partially open at an endopposite bottom wall 1611 such that a mobile device can be receivedtherein.

In other words, carrying case 1601 is configured to receive a mobiledevice “sideways” and/or in a landscape orientation, in contrast tocarrying case 1501 which is configured to receive a mobile device in aportrait orientation.

Attention is next directed to FIG. 17 which depicts views 17-I, 17-II ofan alternative implementation of a carrying case 1701, respectively, ina closed configuration and an open configuration, according tonon-limiting implementations. Carrying case 1701 is generally similar tocarrying case 1201 with like elements having like numbers, howeverpreceded by “17” rather than “12”. Hence, carrying case 1701 comprises:a device holding portion 1702 configured to receive a mobile device (notdepicted, but similar to devices 101, 101 a, 101 b, 101 c), deviceholding portion 1702 comprising at least a front wall 1705 and a gap1706 in front wall 1705 for exposing an indicator of the mobile device,for example as in FIG. 14. Carrying case 1701 further comprises asliding portion 1703 configured to move between a closed position and anopen position, sliding portion 1703 obscuring gap 1706 in the closedposition and exposing at least a portion of gap 1706 in the openposition, sliding portion 1703 being about planar. Sliding portion 1703is in the closed position in view 17-I and in the open position in view17-II.

Device holding portion 1702 generally comprises front wall 1705 and gap1706 therein as well as an opposing back wall 1707, side walls 1709-1,1709-2 joining front wall 1705 to back wall 1707, and a bottom wall 1711such that carrying case 1701 can receive a mobile device therein. Sidewalls 1709-1, 1709-2 will be interchangeably referred to hereafter,collectively, as side walls 1709 and generically as a side wall 1709.While each of front wall 1705, back wall 1707, side walls 1709 andbottom wall 1711 are depicted as being joined to each other along anentirety of each joining edge, in other implementations, front wall1705, back wall 1707, side walls 1709, and bottom wall 1711 can bejoined at only one or more portions of the joining edges. Further eachof front wall 1705, back wall 1707, side walls 1709 and bottom wall 1711can comprise gaps, apertures and the like, other than gap 1706.

However, in these implementations, gap 1706 comprises an aperture infront wall 1705, in contrast to gaps 1206, 1606 which comprise a cut-outof a respective front wall 1205, 1605. In yet further implementations,one or more of gaps 1206, 1606, 1706 can comprise a window, including,but not limited to, a glass window, a plastic window and the like. Insome of these implementations, the window can comprise an aperturecorresponding to a position of speaker 132 c.

Attention is next directed to FIG. 18 which depicts views 18-I, 18-II ofan alternative implementation of a carrying case 1801, respectively, ina closed configuration and an open configuration, according tonon-limiting implementations. Carrying case 1801 is generally similar tocarrying case 1201 with like elements having like numbers, howeverpreceded by “18” rather than “12”. Hence, carrying case 1801 comprises:a device holding portion 1802 configured to receive a mobile device (notdepicted, but similar to devices 101, 101 a, 101 b, 101 c), deviceholding portion 1802 comprising at least a front wall 1805 and a gap1806 in front wall 1805 for exposing an indicator of the mobile device,for example as in FIG. 14. Carrying case 1801 further comprises asliding portion 1803 configured to move between a closed position and anopen position, sliding portion 1803 obscuring gap 1806 in the closedposition and exposing at least a portion of gap 1806 in the openposition, sliding portion 1803 being about planar. Sliding portion 1803is in the closed position in view 18-I and in the open position in view18-II.

Device holding portion 1802 generally comprises front wall 1805 and gap1806 therein as well as an opposing back wall 1807, side walls 1809-1,1809-2 joining front wall 1805 to back wall 1807, and a bottom wall 1811such that carrying case 1801 can receive a mobile device therein. Sidewalls 1809-1, 1809-2 will be interchangeably referred to hereafter,collectively, as side walls 1809 and generically as a side wall 1809.While each of front wall 1805, back wall 1807, side walls 1809 andbottom wall 1811 are depicted as being joined to each other along anentirety of each joining edge, in other implementations, front wall1805, back wall 1807, side walls 1809, and bottom wall 1811 can bejoined at only one or more portions of the joining edges. Further eachof front wall 1805, back wall 1807, side walls 1809 and bottom wall 1811can comprise gaps, apertures and the like, other than gap 1806.

However, in these implementations, gap 1806 comprises an aperture infront wall 1805 that is laterally offset towards side wall 1809-2, andfurther has a length and width less than the length, the length beinggenerally parallel to a longitudinal axis of carrying case 1801.Accordingly, sliding portion 1803 is configured to move between theclosed position of view 18-I and the closed position of view 18-IIlaterally and/or perpendicular to longitudinal axis 1817, as indicatedby arrows 1815-1, 1815-2. Further device holding portion 1802 compriseson opening opposite bottom wall 1811 for receiving a mobile, device in aportrait orientation, along longitudinal axis 1817.

In other words, a location of gap 1806 and sliding portion 1803 isgenerally appreciated to be non-limiting, as long as gap 1806 andsliding portion 1803 correspond to a position of an indicator of adevice and/or at least a portion of a display of the device when thedevice is received in device holding portion 1802.

It is appreciated that heretofore, sliding portions 1203, 1503, 1603,1703 have been described that leave at least a portion of respectivefront walls 1205, 1505, 1605, 1705 exposed, and or visible. However,present implementations are not so limiting.

For example attention is next directed to FIG. 19 which depicts views19-I, 1941 of an alternative implementation of a carrying case 1901,respectively, in a closed configuration and an open configuration,according to non-limiting implementations. Carrying case 1901 isgenerally similar to carrying case 1201 with like elements having likenumbers, however preceded by “19” rather than “12”. Hence, carrying case1901 comprises: a device holding portion 1902 configured to receive amobile device (not depicted, but similar to devices 101, 101 a, 101 b,101 c), device holding portion 1902 comprising at least a front wall(not visible) and a gap 1906 in the front wall for exposing an indicatorof the mobile device, for example as in FIG. 14. Carrying case 1901further comprises a sliding portion 1903 configured to move between aclosed position and an open position, sliding portion 1903 obscuring gap1906 in the closed position and exposing at least a portion of gap 1906in the open position, sliding portion 1903 being about planar. Slidingportion 1903 is in the closed position in view 19-I and in the openposition in view 19-II.

Device holding portion 1902 generally comprises the front wall and gap1906 therein as well as an opposing back wall 1907, side walls 1909-1,1909-2 joining the front wall to back wall 1907, and a bottom wall 1911such that carrying case 1901 can receive a mobile device therein. Sidewalls 1909-1, 1909-2 will be interchangeably referred to hereafter,collectively, as side walls 1909 and generically as a side wall 1909.While each of the front wall, back wall 1907, side walls 1909 and bottomwall 1911 are depicted as being joined to each other along an entiretyof each joining edge, in other implementations, the front wall, backwall 1907, side walls 1909, and bottom wall 1911 can be joined at onlyone or more portions of the joining edges. Further each of the frontwall, back wall 1907, side walls 1909 and bottom wall 1911 can comprisegaps, apertures and the like, other than gap 1906.

However, in these implementations, sliding portion 1903 covers the frontwall in the closed position. Hence, indeed, sliding portion 1903 can beof any size that obscures gaps 1906 when sliding portion 1903 is in theclosed position.

It is further appreciated that while sliding portions described hereinare generally about planar, planar is not to be construed as beingperfectly flat, but merely covering a planar area, for example, gapsdescribed herein. For example, sliding portions described herein canfurther include raised portions, for example for functional and/oraesthetic purposes. Such raised portions can improve a grip on arespective sliding portion for a user to move a sliding portion. Suchraised portions can also provide decorative features that canoptionally, but simultaneously, improve a grip on a respective slidingportion.

While sliding portions and gaps described herein are all generallyrectangular, present implementations are not so limiting and slidingportions and gaps described herein can be one or more of square,circular, rectangular, triangular, a regular shape, an irregular shapeand the like.

Persons skilled in the art will appreciate that there are yet morealternative implementations and modifications possible. For example,attention is next directed to FIG. 20 which depicts views which depictsviews 20-I, 20-II of an alternative implementation of a carrying case2001, respectively, in a closed configuration and an open configuration,according to non-limiting implementations. Carrying case 2001 comprises:a device holding portion 2002 configured to receive a device 101 d(similar to devices 101, 101 a, 101 b, 101 c), a device holding portion2002 (not visible in view 20-II) comprising at least a gap 2006 forexposing an indicator of device 101 d. Carrying case 2001 furthercomprises a sliding portion 2003 configured to move between a closedposition and an open position, sliding portion 2003 obscuring gap 2006in the closed position and exposing at least a portion of gap 2006 inthe open position, sliding portion 2003 being about planar. Slidingportion 2003 is in the closed position in view 20-I and in the openposition in view 20-II.

In implementations depicted in FIG. 21, sliding portion 2003 furthercomprises a raised decorative portion 2099, which can also be used toimprove a user's grip on carrying case 2001; indeed, raised decorativeportion 2099 illustrates that while sliding portion 2003 is generallyabout planar, such planarity can include raised portions at least on anexterior of sliding portion 2003.

With reference to FIG. 21, which depicts device holding portion 2002without sliding portion 2003, device holding portion 2002 generallycomprises a back wall 2007. side walls 2009-1, 2009-2, and a bottom wall2011 such that carrying case 2001 can receive a mobile device therein.Side walls 2009-1, 2009-2 will be interchangeably referred to hereafter,collectively, as side walls 2009 and generically as a side wall 2009.While each of back wall 2007, side walls 2009 and bottom wall 2011 aredepicted as being joined to each other along an entirety of each joiningedge, in other implementations, back wall 2007, side walls 2009, andbottom wall 2011 can be joined at only one or more portions of thejoining edges. Further each of back wall 2007, side walls 2009 andbottom wall 2011 can comprise gaps, apertures and the like, other thangap 2006.

In any event, in these implementations, device holding portion 2002 doesnot comprise a front wall, but rather gap 2006 is formed by side walls2009 and bottom wall 2011. Put another way, a front section of deviceholding portion 2002 is open and forms gap 2006.

From FIG. 21 it is further apparent that side walls 2009 of deviceholding portion 2002 comprise opposing biased portions 2101 extendinglaterally towards each other for frictionally retaining device 101 dwhen received therein.

Attention is now directed to FIG. 22 which depicts a perspective view ofcarrying case 2001 with device 101 d received in device holding portion2002, and sliding portion 2003 in the open position. Side wall 2009-1 ofdevice holding portion 2002 is also visible in FIG. 22. From FIG. 22, itis further apparent that while sliding portion 2003 is generally planar,sliding portion 2003 further comprises side walls 2209 (though only oneof which is visible in FIG. 22) that comprise rails 2250-1 complimentaryto rails 2250-2 at side walls 2209 of device holding portion 2002. It isfurther appreciated that rails 2250-1, 2250-2 interlock and sliderelative to one another such that sliding portion 2003 moves between theclosed position and the open position on rails 2250-1, 2205-2. Whilerails 2250-1, 2250-2 are only depicted on one side of carrying case2001, it is appreciated that each of sliding portion 2003 and deviceholding portion 2002 comprise corresponding similar rails at opposingsidewalls 202209, 2009-2. In other words, sliding portion 2003 comprisesside walls 2209 that slide along corresponding side walls 2209 of deviceholding portion 2002.

From FIG. 22 it is apparent that while sliding portion 2003 is aboutplanar, sliding portion 2003 also comprises side walls 2209 and a bottomwall 2211 which are generally perpendicular to the remainder of slidingportion 2003. Indeed, decorative portion 2099, raised side walls 2209and a bottom wall 2211 illustrate that while sliding portion 2003 isgenerally about planar, such planarity can include functional and/ordecorative elements extending there from.

Attention is next directed to FIG. 23, which is substantially similar toFIG. 4, with like elements having like numbers, however with an “e”appended thereto rather than an “a”. FIG. 23 depicts a device 101 ecomprising a housing 109 e, which houses a processor 120 einterconnected with a memory 122 e; a communications interface 124 e(interchangeably referred to as interface 124 e); an indicatorcomprising a display 126 e for providing notifications; an input device128 e; a speaker 132 e; at least one microphone 134 e; and an indicator135 e. While not depicted, device 101 e can further comprise a seconddetector similar to detector 139 for detecting when a carrying case inwhich device 101 e is received is in an open configuration or a closed aconfiguration.

However, in these implementations, microphone 134 e is generally enabledto detect a sound pattern produced when device 101 e is received in acarrying case, as described below. Furthermore, processor 120 e isgenerally configured to determine that device 101 e is received in acarrying case when at least one microphone 134 e detects the soundpattern. Hence, memory 122 e can store an application 145 e that, whenprocessed by processor 120 e (as depicted) causes processor 120 e to beconfigured to determine that device 101 e is received in a carrying casewhen at least one microphone 134 e detects the sound pattern. Memory 122e can further store a sound pattern 2301 that can be compared to a soundpattern detected by microphone 134 e to determine whether device 101 eis received in a carrying case.

Hence, it is appreciated that, in these implementations, microphone 134e can be similar to first detector 137 in that microphone 134 e isgenerally enabled to detect when device 101 e is received in a carryingcase. Thus, method 300 can also be implemented in device 101 e(presuming device 101 e comprises a detector similar to detector 139)wherein block 301 is implemented using microphone 134 e, block 301comprising detecting when device 101 e is mated with a carrying case byreceiving a sound pattern detected by microphone 134 e similar to soundpattern 2301. As will be presently described, the sound pattern detectedby microphone 134 e is generally produced by actuator bumps on one ormore of device 101 e and a carrying case, the actuator bumps configuredto interact with the other of device 101 e and the carrying case whendevice 101 e is received in the carrying case to produce a sound patterndetectable by at least one microphone 134 e.

Attention is hence next directed to FIG. 24 which depicts a system 2400comprising: device 101 e comprising at least one microphone 134 e andprocessor 120 e (not depicted in FIG. 24, but nonetheless understood tobe present); and a carrying case 2401 configured to receive device 101e, one of device 101 e and carrying case 2401 comprising actuator bumps2403 configured to interact with the other of device 101 e and carryingcase 2401 when device 101 is received in carrying case 2401 to produce asound pattern detectable by at least one microphone 134 e, processor 120e configured to determine that device 101 e is received in carrying case2401 when at least one microphone 134 e detects the sound pattern.Receipt of device 101 e into carrying case 2401 is indicated by arrow2404.

Further, in implementations depicted in FIG. 24, actuator bumps 2403 arelocated on an interior wall 2405 of carrying case 2401, as indicated byactuator bumps 2403 being depicted in stippled lines (i.e. an exteriorof carrying case 2401 is depicted in FIG. 24 and actuator bumps 2403 arelocated on interior wall 2405, hence actuator bumps 2403 would not bevisible in the view depicted in FIG. 24). Specifically, actuator bumps2403 are located on interior wall 2405 of carrying case 2401 such thatactuator bumps 2403 interact with at least one microphone 134 e toproduce the sound pattern.

Attention is next directed to FIG. 25, which depicts a perspective view25-I of interior wall 2405, independent of carrying case 2401, andactuator bumps 2403, as well as a cross-sectional view 25-II of interiorwall 2405 along line A-A through actuator bumps 2403. From view 25-II itis apparent that actuator bumps 2403 can comprises one or more of bumps,protuberances, nodules and the like that extend from interior wall 2405and that are located along a line on an interior wall 2405, for example,line A-A.

View 25-II further depicts microphone 134 e as device 101 e is received(e.g. inserted) in carrying case 2401, microphone 134 e interacting withactuator bumps 2403. While the remainder of device 101 e is not depictedin FIG. 25, it is appreciated to be nonetheless present. As device 101 eis inserted into carrying case 2401, microphone 134 e brushes againsteach of actuator bumps 2403 producing a sound pattern 2501, alsodepicted in view 25-II. Hence, actuator bumps 2403 have a height thatenables actuator bumps 2403 to interact with/brush up against microphone134 e to produce sound pattern 2501.

Peaks in sound pattern 2501 generally correspond to actuator bumps 2403on a one-to-one basis, and valleys in sound pattern 2501 correspond toareas between actuator bumps 2403 on a one-to-one basis. While peaks ofsound pattern 2501 are depicted as a series of square waves, it isappreciated that peaks of sound pattern 2501 can have any shapeproduceable by microphone 134 e interacting with/brushing againstactuator bumps 2403.

Furthermore, one or more of a length of actuator bumps 2403 and adistance between actuator bumps 2403 can be configured such that soundpattern 2501 is respective to one or more of carrying case 2401, a classof carrying case 2401 and a type of carrying case 2401. In other words,one or more of carrying case 2401, a class of carrying case 2401 and atype of carrying case 2401 can be identified and/or uniquely identifiedusing sound pattern 2501. For example, the longer a given actuator bump2403 is along a length of line A-A, the wider a corresponding peak insound pattern 2501; similarly, the longer a distance between adjacentactuator bumps 2403 along a length of line A-A, the wider acorresponding valley in sound pattern 2501.

In yet further implementations, one or more actuator bumps 2403 canextend further from interior wall 2405 than other actuator bumps 2403such that peaks of sound pattern 2501 can also vary. In other words, aheight of each actuator bump 2403 can be varied.

Hence, one or more of a length of actuator bumps 2403, a distancebetween actuator bumps 2403, and a height of actuator bumps 2403 can beconfigured such that the sound pattern is respective to one or more ofcarrying case 2401, a class of carrying case 2401 and a type of carryingcase 2401. In other words, actuator bumps 2403 can be configured similarto a bar code and the like to convey information in the form of soundpattern 2501 to device 101 e that, for example, identifies one or moreof carrying case 2401, a class of carrying case 2401 and a type ofcarrying case 2401. For example, sound pattern 2501 can be indicative ofan orientation configuration of carrying case 2401 (e.g. indicative ofcarrying case 2401 receiving device 101 e in a portrait orientation, asdepicted a landscape orientation, and the like), whether carrying case2401 comprises a flap, similar to carrying case 201, whether carryingcase 2401 comprises a sliding portion, similar to carrying case 1501,and the like. Indeed, it is appreciated that each carrying casedescribed herein can be adapted to include actuator bumps that arerespective to each carrying case such that the carrying case can beidentified.

As such, while depicted implementations include five actuator bumps2403, other implementations can include fewer than five actuator bumpsor more than five actuator bumps. In general, present implementationscan include any number of actuator bumps for producing a sound patternthat can be detected by microphone 134 e such that processor 120 e candetermine that device 101 e is being received in carrying case 2401, orthe like.

Further, the area between actuator bumps 2403 can also extend frominterior wall 2405, but to a lesser extent than actuator bumps 2403,such that actuator bumps 2403, and the areas in between comprise a ridgeextending from interior wall 2405.

In yet further implementations, actuator bumps 2403 located on interiorwall of carrying case 2401 and sound pattern 2501 can be respective toone or more of carrying case 2401, a class of carrying case 2401 and atype of carrying case 2401, and processor 120 e can be configured toplace device 101 e into a given notification mode based on sound pattern2501.

As depicted, actuator bumps 2403 are asymmetrically positioned such thata second sound pattern produced when device 101 e is removed fromcarrying case 2401 is different from sound pattern 2501 produced whendevice 101 e is received in carrying case 2401 and processor 120 e candetermine when device 101 e is inserted and removed from carrying case2401 based on whether sound pattern 2501 or the second sound pattern isdetected.

However, actuator bumps 2403 need not be asymmetric, and can, forexample be symmetric such that the same sound pattern is detected whendevice 101 e is inserted and removed from carrying case 2401; in theseimplementations, processor 120 e can be configured to determine thatdevice 101 e is received in carrying case 2401 when at least onemicrophone 134 e detects the sound pattern a first time and determinethat that device 101 e is received in carrying case 1401 when at leastone microphone 134 e detects the sound pattern a second time.

Attention is next directed to FIG. 26 which is similar to FIG. 23, withlike elements having like numbers, depicting processor 120 e receivingsound pattern 2501 using microphone 134 e and comparing sound pattern2501 with sound pattern 2301 stored in memory 122 e. When sound patterns2301, 2501 match, as depicted, processor 120 e can determine that device101 e is received in carrying case 2401. When sound patterns 2301, 2501do not match, processor 120 e does not determine that device 101 e isreceived in carrying case 2401. In other words, sound pattern 2301 canbe stored at memory 122 e such that processor 120 e can determine whendevice 101 e is received in carrying case 2401. While not depicted,memory 122 e can store a plurality of sound patterns corresponding toone or more of different carrying cases, different classes of carryingcases and different classes of carrying cases such that one or more ofthe different carrying cases, different classes of carrying cases anddifferent classes of carrying cases can be identified. It is assumed, inthese implementations, that a given carrying case corresponding to asound pattern stored in memory 122 e comprises actuator bumps similar toactuator bumps 2403, but respective the given carrying case. Hence, oncea carrying case into which device 101 f is being received is identified,and the carrying case has an open configuration and a closedconfiguration, when block 305 of method 300 is implemented, the givennotification mode implemented can be respective to the identifiedcarrying case.

Attention is hence next directed to FIG. 27 which depicts a system 2700comprising: device 101 f comprising at least one microphone 134 f-1 anda processor (not depicted in FIG. 27, but nonetheless understood to bepresent and further understood to be similar to processor 120 e); and acarrying case 2701 configured to receive device 101 f, one of device 101f and carrying case 2701 comprising actuator bumps 2703 configured tointeract with the other of device 101 f and carrying case 2701 whendevice 101 is received in carrying case 2701 to produce a sound patterndetectable by at least one microphone 134 f-1, the processor of device101 f configured to determine that device 101 f is received in carryingcase 2701 when at least one microphone 134 f-1 detects the soundpattern. Receipt of device 101 f into carrying case 2701 is indicated byarrow 2704.

Indeed, device 101 f is generally similar to device 101 e, howeverdevice 101 f further comprises an actuator 2750 configured to interactwith actuator bumps 2703 to produce the sound pattern. In theseimplementations, actuator 2750 can comprise one or more of a bump, aprotuberance, a nodule and the like that extends from side of device 101f, as depicted an edge wall of device 101 f. As depicted, actuator 2750is located along a long edge and/or a side wall and/or side edge ofdevice 101 f.

Further, in implementations depicted in FIG. 27, actuator bumps 2703 arelocated on an interior wall 2705 of carrying case 2701, as indicated byactuator bumps 2703 being depicted in stippled lines (i.e. an exteriorof carrying case 2701 is depicted in FIG. 27 and actuator bumps 2703 arelocated on interior wall 2705, hence actuator bumps 2703 would not bevisible in the view depicted in FIG. 27). Specifically, actuator bumps2703 are located on a side interior wall 2705 of carrying case 2701 suchthat actuator bumps 2703 interact with actuator 2750 to produce thesound pattern. Indeed, actuator bumps 2703 and actuator 2750 arelocated, respectively, on carrying case 2701 and device 101 f so thatthey interact with each other. Actuator bumps 2703 are otherwise similarto actuator bumps 2403.

In other words, in these implementations, actuator bumps 2703 do notinteract with microphone 134 f-1 directly; rather the sound pattern,similar to sound pattern 2501, is produced by actuator 2750 interactingwith actuator bumps 2703. Hence, at least one microphone 134 f-1 islocated to detect the sound pattern when actuator 2750 interacts withactuator bumps 2703. Indeed, actuator bumps 2703 are configured toproduce the sound pattern above a noise floor of at least one microphone134 f-1.

Alternatively, as depicted, device 101 f can comprise at least a secondmicrophone 134 f-2 located to detect the sound pattern when actuator2750 interacts with actuator bumps 2750. Indeed, in theseimplementations, actuator bumps 2703 are configured to produce the soundpattern above a noise floor of at least one microphone 134 f-2. In theseimplementations, second microphone 134 f-2 can be located about adjacentand/or about proximal to actuator 2750. In yet further implementations,the sound pattern produced by actuator 2750 interacting with actuatorbumps 2703 can be detected by a combination of at least one microphone134 f-1 and second microphone 134 f-2. In yet further implementations,device 101 f can comprise yet further microphones for detecting thesound pattern.

However, second microphone 134 f-2 can be optional. Hence, themicrophone used to detect the sound pattern can be one of furtherconfigured to receive voice data during a call at device 101 f (i.e.microphone 134 f-1); and different from another microphone configured toreceive the voice data during a call at device 101 f (i.e. secondmicrophone 134 f-2 can be configured to detect the sound pattern whileat least one microphone 134 f-1 can be used for receiving voice dataduring a call). Regardless the at least one microphone used to detectthe sound patter can be located at one or more of towards a top ofdevice 101 f, towards a bottom of device 101 f, adjacent a speaker ofdevice 101 f, and a long an edge of device 101 f.

In yet further implementations, sliding portions of carrying casesdescribed heretofore (e.g. sliding portions 1113, 1203, 1503 1603 andthe like) can be configured with actuator bumps similar to actuatorbumps 2503 which can produce a sound pattern detectable by acomplementary device when the sliding portions are opened and closed.Hence, such sound patterns can be used to detect when a sliding portionand/or a carrying case is in an open configuration. In other words,block 303 of method 300 can also be implemented using sound patterns.

Attention is next directed to FIG. 28 which depicts a system 2800comprising: device 101 g comprising at least one microphone 134 g-1 anda processor (not depicted in FIG. 28, but nonetheless understood to bepresent and further understood to be similar to processor 120 e); and acarrying case 2801 configured to receive device 101 g, one of device 101g and carrying case 2801 comprising actuator bumps 2803 configured tointeract with the other of device 101 g and carrying case 2801 whendevice 101 is received in carrying case 2801 to produce a sound patterndetectable by at least one microphone 134 g-1, the processor of device101 g configured to determine that device 101 g is received in carryingcase 2801 when at least one microphone 134 g-1, and/or optionally asecond microphone 134 g-2, detects the sound pattern. Receipt of device101 g into carrying case 2801 is indicated by arrow 2804.

Indeed, device 101 g is generally similar to device 101 e, however inthese implementations device 101 g further comprises actuator bumps 2803configured to interact with an interior wall 2805 of carrying case 2801to produce the sound pattern, and specifically an actuator 2850 locatedon interior wall 2805. Indeed, it is appreciated that system 2800 issimilar to system 2700 however actuator bumps 2803 are located at device101 g and actuator 2850 is located at carrying case 2801. Further, theproduce a sound pattern similar to sound pattern 2501, positions ofactuator bumps 2803 are reversed by about 180° relative to actuatorbumps 2703.

It is further assumed in implementations described herein that one ormore microphones for detecting a sound pattern can be “always on” and/oron when detecting a sound pattern. However, it is further appreciatedthe microphones can be turned off, for example, by a respectiveprocessor, when entering a carrying case mode; however, when the one ormicrophones are configured to detect a sound pattern when a respectivedevice is being removed from a carrying case, at least one microphone ata respective device can be on in a carrying case mode and/or “alwayson”. It is further appreciated that microphones described herein fordetecting a sound pattern can be directional (e.g. for detecting a soundpattern in a given direction) or omnidirectional.

It is yet further appreciated that devices described herein that usesound patterns to determine when being received and/or removed from acarrying case can further comprise codecs and/or digital signalprocessors (DSPs) for encoding and/or decoding sound patterns and thelike. In some of these implementations, processors described herein canbe combined with DSPs.

While implementations described herein have depicted actuator bumpslocated at one or the other of a device and a carrying case, in yetfurther implementations the actuator bumps can be distributed betweenthe device and the carrying case and/or located at both the device andthe carrying case. Indeed, each of a device and a complementary carryingcase can comprise actuator bumps that can interact with each other toproduce a sound pattern. In yet further implementations, one or more ofa device and a complementary carrying case can comprise more than oneset and/or line of actuator bumps such that more than one sound patterncan be produced when the device is being received in the carrying case;indeed, the sound patterns can hence be detected in stereo and/or fromdifferent directions and/or by different microphones at the device. Suchdirectionality can also be used to identify the carrying case, asdescribed above, and respective notification mode accordinglyimplemented at the device.

Hence, it is appreciated that a sound pattern can be produced that canbe used to detect when a device is being received in a complementarycarrying case, the sound pattern produced when the device is beingreceived in the carrying case. Optionally a second sound pattern and/orthe same sound pattern can be produced when the device is being removedfrom the carrying case. The sound pattern can be produced by actuatorbumps located at the device and/or the carrying case, and further thesound pattern can be used to place the device in a given notificationmode.

While is appreciated that the methods described herein could also beused with non-portable devices, the methods may be especiallyadvantageous for mobile electronic devices that are handheld.Implementation of one or more embodiments may realize one or moreadditional benefits as well, such as flexibility of implementation.Further, this disclosure can be adapted to a variety of mobileelectronic devices, a variety of carrying cases and/or holsters, and avariety of bodies, including, but not limited to, planar bodies andskins with open configurations and closed configurations.

Hence, provided herein are various implementations of carrying cases,and device that can provide notifications when mated with the carryingcases, when the carrying case is in an open configuration. Whennotifications are provided at a respective display of the devices, whenthe carrying case is in the open configuration, the methods can beuseful for providing a “peek” at the display and/or notificationsprovided at the display, for example in a status bar. In other words,the carrying case can be placed, even temporarily, in the openconfiguration, so that notifications at the device can be viewed, ratherthan take the device out of the carrying case, even partially, to seenotifications. Indeed, in implementations where an indicator light isvisible at the device while the device is in the carrying case, therebyprompting a user to check notifications at the device, the “peek” at thedisplay can provide the user with more information on the notificationswithout the user removing the device from the carrying case.

It is further appreciated that carrying cases described herein provide aconvenient receptacle for holding/interacting with a device, whilesimultaneously providing a mechanism to view notifications withoutremoving the device from the carrying case. Further advantages ofdevices described herein include, but are not limited to versatility inproviding notifications at a device mated with a carrying case,adaptability to a variety of devices, combined functionality of anotification devices and a physical protector, compactness, light weight(such that carrying case is portable, thereby supporting handheldimplementations and aiding mobility and portability), efficiency,robustness, and enhancing the functionality of a device mated theretowithout detracting from other functions of the device.

Those skilled in the art will appreciate that in some implementations,the functionality of devices 101, 101 a, 101 b, 101 c, 101 d, 101 e, 101f, 1010 g can be implemented using pre-programmed hardware or firmwareelements (e.g., application specific integrated circuits (ASICs),electrically erasable programmable read-only memories (EEPROMs), etc.),or other related components. In other implementations, the functionalityof devices 101, 101 a, 101 b, 101 c, 101 d, 101 e, 101 f, 1010 g can beachieved using a computing apparatus that has access to a code memory(not shown) which stores computer-readable program code for operation ofthe computing apparatus. The computer-readable program code could bestored on a computer readable storage medium which is fixed, tangibleand readable directly by these components, (e.g., removable diskette,CD-ROM, ROM, fixed disk, USB drive). Furthermore, it is appreciated thatthe computer-readable program can be stored as a computer programproduct comprising a computer usable medium. Further, a persistentstorage device can comprise the computer readable program code. It isyet further appreciated that the computer-readable program code and/orcomputer usable medium can comprise a non-transitory computer-readableprogram code and/or non-transitory computer usable medium.Alternatively, the computer-readable program code could be storedremotely but transmittable to these components via a modem or otherinterface device connected to a network (including, without limitation,the Internet) over a transmission medium. The transmission medium can beeither a non-mobile medium (e.g., optical and/or digital and/or analogcommunications lines) or a mobile medium (e.g., microwave, infrared,free-space optical or other transmission schemes) or a combinationthereof.

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by any one of the patentdocument or patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightswhatsoever.

Persons skilled in the art will appreciate that there are yet morealternative implementations and modifications possible, and that theabove examples are only illustrations of one or more implementations.The scope, therefore, is only to be limited by the claims appendedhereto.

What is claimed is:
 1. A carrying case comprising: a device holdingportion configured to receive a mobile device, the device holdingportion comprising a gap for exposing an indicator of the mobile device;and a sliding portion configured to move between a closed position andan open position, the sliding portion obscuring the gap in the closedposition and exposing at least a portion of the gap in the openposition, the sliding portion being about planar.
 2. The carrying caseof claim 1, wherein, the device holding portion comprises at least afront wall and the gap is located in the front wall.
 3. The carryingcase of claim 1, wherein the gap comprises one or more of an aperture ina front wall of the device holding portion, a cut-out of the front walland an opening of the front wall.
 4. The carrying case of claim 1,wherein the device holding portion comprises a longitudinal axis and thedevice holding portion is configured to receive the mobile device alongthe longitudinal axis.
 5. The carrying case of claim 4, wherein thesliding portion is configured to move between the closed position andthe open position along the longitudinal axis.
 6. The carrying case ofclaim 1, further comprising a biasing mechanism configured to bias thesliding portion to at least the closed position.
 7. The carrying case ofclaim 1, wherein the sliding portion is biased towards the closedposition.
 8. The carrying case of claim 1, wherein the sliding portionis biased towards both the closed position and the open position suchthat when the sliding portion is displaced from either of the closedposition and the open position, the sliding portion moves to one of theclosed position and the open position depending on a position of thesliding portion relative to the device holding portion.
 9. The carryingcase of claim 1, further comprising a biasing mechanism configured tobias the sliding portion to both the closed position and the openposition such that the sliding portion moves to one of the closedposition and the open position depending on a position of the slidingportion relative to the device holding portion.
 10. The carrying case ofclaim 1, further comprising a biasing mechanism configured to move thesliding portion to the closed position when the sliding portion is movedmore than halfway from the open position towards the closed position;and, move the sliding portion to the open position when the slidingportion is moved more than halfway from the closed position towards theopen position.
 11. The carrying case of claim 1, further comprising abiasing mechanism configured to bias the sliding portion to at least theclosed position.
 12. The carrying case of claim 1, wherein the slidingportion is configured to be frictionally retained at positions betweenthe closed position and the open position.
 13. The carrying case ofclaim 1, wherein a size of the sliding portion is about a same size asthe gap.
 14. The carrying case of claim 1, wherein the sliding portioncovers a front wall of the device holding portion in both the openposition and the closed position, the front wall comprising the gap. 15.The carrying case of claim 1, wherein the sliding portion comprises sidewalls that slide along corresponding side walls of the device holdingportion.
 16. The carrying case of claim 1, wherein the sliding portionis configured to be operated with one hand.
 17. The carrying case ofclaim 1, further comprising one or more apertures in at least one of thedevice holding portion and the sliding portion, the one more aperturescorresponding to one or more of a position of a speaker and a microphoneof the mobile device, when the mobile device is received by the deviceholding portion.